DataBK.COM

• All versions of Microsoft SQL Server backup and restore supports: Microsoft SQL Server 7.0 ,Microsoft SQL Server 2000 , Microsoft SQL Server 2005 , 2008 supports , MSDE , WMSDE , SQL Server 2005, 2008 Express and Enterprise Edition .
   
• Remote management supports.
   
• Back up multiple databases in one single job.
   
• Log shipping supports in professional edition.
   
• Flexible backup strategies supports , basic on backup counter or backup size.
   
• More flexible email notification option.
   
• It can be configured to do extra command ,works before or after job.
   
• Copy database from one server to another by creating backups automatically in professional edition.
   
• More easy to restore database to a refresh machine or other server in professional edition.
   
• Convert DataBK backups to Microsoft SQL Server raw backups.
   
• Multiple users supports.
   
• Multi SQL Server instance supports.
   
• Remote Storage Server run as service.
   
• Supports database full and differential backup and transaction log backup.
   
• Data compression supports.
   
• AES encryption supports.
   
• Backup to local hard disk , USB removable disk or remote network driver .
   
• Restore database with a new database name.
   
• Restore database to a point in time.
   
• Restore database to point of failure.

Yes , SQL Server Backup supports backing up Microsoft SQL Server 2008 and 2008 Express .
In sql server instance configuration window , you 'll see this features :

Restoring master database requires the SQL Server running in single user mode. To start SQL Server in single user mode :

• Open "Control Panel->Administrative Tools->Services"
  
  
• Mouse right click on specified SQL Server instance service and select "Properties" menu to bring up following configuration window:
  
  
• Specify start parameters as following:

  -s{ Instance name } -m

  If instance is default instance (no instance name) ,then just enter

• For early version of SQL Server (SQL Server 2000 or earlier version) , you have to use special way to back up the full text catalog because it can not be backed up along with database during a normal backup operation .
• But for a 2005 edition , (including SQL Server 2005 , Express 2005) , you can back up the full text catalog via a database full backup operation , the full text catalog is treated as parts of database files.

A key feature of SQL Server Backup is that it can delete expired backup automatically . This feature can save and reuse your storage space , need not worry about the storage space problem.

When a job's backup is expired, it is deleted at the end of the job . If this job dose not run, it will not be deleted.

Importance:

• Please ensure you have a latest full backup , or the database can be risky ,because database restoration required a full backup at least.

• Transaction log backup is a backup for log files of a database .
• Backing up the transaction log periodically to create a sequence of transaction log backups offers users the most flexibility in restoring databases.

• A relatively small portion of the data in the database has changed since the last database backup. Differential database backups are most efficient if the same data is modified frequently.
• You are using the Simple Recovery model, which does not permit Transaction log backups, and you want to perform backups more frequently than is practical for full database backups.
• You are using the Full or Bulk-Logged Recovery model and want to minimize the time it takes to roll forward Transaction log backups when restoring a database.

You need to perform a full database backup immediately after you have performed any one of the following actions, or you may be unable to use that backup with your last full database backup to restore the database successfully .

• Created a new database
• Changed the recovery model of the database
• Changed the number of files or file groups in the database
• Changed the arrangement of files among the file groups
• Canceled a full backup job while it is running

One or more following operations occur , Please backup the master database.

• Creating or deleting a user database.
• If a user database grows automatically, by virtue of the autogrow feature, to accommodate new data, this does not affect master. Adding and deleting files and filegroups does not affect master.
• Adding logins or other login security-related operations.
• Database security operations, such as adding a user to a database, do not affect master.