Sql Server

SMS (Short Messaging Service)

SMS or the Short Messaging Service allows users to send and receive personal text messages directly between mobile phones or sometimes to email adresses. Each message can be up to 160 characters long (when using the default character set) and can be sent to and from users of different operator networks. All mobile phones support SMS.
Recently mobile manufacturers have started offering special reading layouts for SMS inspired by Instant Messengers such as ICQ, Skype, and MSN. The so-called threaded message layout or conversation-style layout displays the incoming and outgoing messages between two participants in a single pane ordered chronologically.
This enhancement reflects the recently prevalent use of SMS as a type of instant messaging much like you would chat on a computer. When possible we try to explicitly state that a mobile phone supports this enhanced messaging view.

SQL Server Management Studio

SQL Server Management Studio

• Right click on the database name
• Select Tasks > Backup
• Select "Full" as the backup type
• Select "Disk" as the destination
• Click on "Add..." to add a backup file and type "C:\AdventureWorks.BAK" an click "OK"
• Click "OK" again to create the backup

transaction log backup allows you to backup the active part of the transaction log.  So after you issue a "Full" or "Differential" backup the transaction log backup will have any transactions that were created after those other backups completed.  After the transaction log backup is issued, the space within the transaction log can be reused for other processes.

SQL Server Management Studio

• Right click on the database name
• Select Tasks > Backup
• Select "Transaction Log" as the backup type
• Select "Disk" as the destination
• Click on "Add..." to add a backup file and type "C:\AdventureWorks.TRN" and click "OK"
• Click "OK" again to create the backup

Another option for backing up your databases is to use "File" backups.  This allows you to backup each file independently instead of having to backup the entire database.  This is only relevant when you have created multiple data files for your database

SQL Server Management Studio

• Right click on the database name
• Select Tasks > Backup
• Select either "Full" or "Differential" as the backup type
• Select "Files and filegroups"
• Select the appropriate file and click "OK"

A new option is "Partial" backups which was introduced with SQL Server 2005.  This allows you to backup the PRIMARY filegroup, all Read-Write filegroups and any optionally specified files.  This is a good option if you have Read-Only filegroups in the database and do not want to backup the entire database all of the time

SQL Server Management Studio

How to set using SQL Server Management Studio

• Right click on database name and select Properties
• Go to the Options page
• Under Recovery model select "Bulk-logged"
• Click "OK" to save

The advantage of using the "Bulk-logged" recovery model is that your transaction logs will not get that large if you are doing bulk operations and it still allows you to do point in time recovery as long as your last transaction log backup does not include a bulk operation

WAP

WAP (Wireless Application protocol)

WAP is an international standard for applications that use wireless communication. Its most common application is to enable access to the Internet from a mobile phone or a PDA.

WAP sites are websites written in or converted to WML (Wireless Markup Language) and accessed via the WAP browser

WAP websites are now considered outdated as most modern phones have web browsers with HTML support.

WAP

WAP (Wireless Application protocol)

WAP is an international standard for applications that use wireless communication. Its most common application is to enable access to the Internet from a mobile phone or a PDA.

WAP sites are websites written in or converted to WML (Wireless Markup Language) and accessed via the WAP browser

WAP websites are now considered outdated as most modern phones have web browsers with HTML support.

Edge-Networking

EDGE (also known as Enhanced GPRS or EGPRS) is a data system used on top of GSM networks. It provides nearly three times faster speeds than the outdated GPRS system. The theoretical maximum speed is 473 kbps for 8 timeslots but it is typically limited to 135 kbps in order to conserve spectrum resources. Both phone and network must support EDGE, otherwise the phone will revert automatically to GPRS.
EDGE meets the requirements for a 3G network but is usually classified as 2.75G.
Enhanced Data rates for GSM Evolution (EDGE) (also known as Enhanced GPRS (EGPRS), or IMT Single Carrier (IMT-SC), or Enhanced Data rates for Global Evolution) is a digital mobile phone technology that allows improved data transmission rates as a backward-compatible extension of GSM. EDGE is considered a 3G radio technology and is part of ITU's 3G definition.^[1] EDGE was deployed on GSM networks beginning in 2003 — initially by Cingular (now AT&T) in the United States.^[2]
EDGE is standardized by 3GPP as part of the GSM family.
Through the introduction of sophisticated methods of coding and transmitting data, EDGE delivers higher bit-rates per radio channel, resulting in a threefold increase in capacity and performance compared with an ordinary GSM/GPRS connection.
EDGE can be used for any packet switched application, such as an Internet connection.
Evolved EDGE continues in Release 7 of the 3GPP standard providing reduced latency and more than doubled performance e.g. to complement High-Speed Packet Access (HSPA). Peak bit-rates of up to 1Mbit/s and typical bit-rates of 400kbit/s can be expected.

Recovery Model

Three types of recovery models

The three types of recovery models that you can choose from are:

• Full
• Simple
• Bulk-Logged

Each database can have only one recovery model, but each of your databases can use a different recovery model, so depending on the processing and the backup needs you can select the appropriate recovery model per database.  The only exception to this is the TempDB database which has to use the "Simple" recovery model.

Also, the database recovery model can be changed at any time, but this will impact your backup chain, so it is a good practice to issue a full backup after you change your recovery model.

Diiference between OODBMS and ORDBMS

Definition:

Object-Relational databases extend the Relational Data Model

to address those weaknesses identified previously.

An Object-Relational database adds features associated with

object-oriented systems to the Relational Data Model.

MAJOR DIFFERENCE BETWEEN AN

ORDBMS AND AN OODBMS

OODBMSs try to add DBMS functionality to one

or more OO programming languages.

ORDBMSs

REVOLUTIONARY IN THAT THEY ABANDON SQL

ORDBMSs try to add richer data types and OO

features to a relational DBMS.

EVOLUTIONARY IN THAT THEY EXTEND SQL

CONSIDERATIONS

OODBMS - put more emphasis on the role of the client, i.e.,

Client side caching! This can radically improve long, process

intensive, transactions.       

ORDBMS - SQL is still the language for data definition,

manipulation and query – Still have Impedance Mismatch!

OODBMSs have been optimised to directly support objectoriented

applications and specific OO languages.

ORDBMSs are supported by most of the ‘major players’ in

the DBMS market place.       

Thanks to the Internet, the legal need to keep track of lots of business information, new marketing methods, and the explosion of data-intensive scientific progress, databases are being used more than ever before for storing and accessing information. There are currently three different models in use for database management systems: relational, object-oriented, and object-relational. This article introduces all three, and discusses their relative strengths and weaknesses.