Restoration Best Practices

This topic lists the best practices for restoring Commerce Server.

Restrict access to the database before you restore backup.

It is important to restrict access to a database before restoring it. Set the Members of db_owner, dbcreator, or sysadmin database option to True.
Backup the transaction log file before you restore backup.

Back up the transaction log file to ensure database consistency. The transaction log file backup is used to recover the database as the last step in the restore process. If you do not back up the transaction log file before you restore backups, you will lose any data modifications that occurred between the last transaction log file backup and the time when the database was taken offline.
Verify your backup files.

Use the Transact-SQL statements RESTORE HEADERONLY, RESTORE FILELISTONLY, RESTORE LABELONLY, and RESTORE VERIFYONLY to verify backup files before you restore them.
Restore backups in the correct order.

If you have created different types of backups, you must restore them in the correct order to prevent data loss. Restore backups in the following order:
1. Most recent full database backup
2. Most recent differential backup
3. Most recent transaction log file backup
Specify the RECOVERY or NORECOVERY option.

Specify the RECOVERY or NORECOVERY option to prevent administrative errors during the restore process and to make the statement easier to read. The RECOVERY option is the SQL Server default.

Additional resources