Working with Restore Sequences for SQL Server Databases

SQL Server 2005 restore can be used to accomplish simple operations quickly and easily, yet it gives you the control to restore the minimum data necessary in the least time. The topics in this section describe how you can combine multiple RESTORE statements into restore sequences that copy data, roll it forward, and bring it online at the end of the rollback phase.


For an introduction to the redo phase, during which roll forward occurs, see Understanding How Restore and Recovery of Backups Work in SQL Server.

Catalog views, the msdb database, and backups contain necessary information for constructing a valid restore sequence, such as the log sequence numbers at which a backup set starts and ends. Catalog views also provide information about the state of the database and associated files. This state information helps you determine the next step to take when you are restoring data.

In This Section

  • Log Sequence Numbers and Restore Planning
    Discusses the most important log sequence numbers for creating a log chain. This topic is relevant only for databases using the full or bulk-logged recovery models.
  • Recovery Paths
    Discusses issues related to restoring a database to an earlier point in time using differential or log backups.
  • Advanced Considerations for Restore Sequences
    Discusses issues such as changing a roll forward set, skipping roll forward of data in read-only files, using multiple full backups, executing backup and restore at the same time in a database, controlling creation of added files during roll forward, restoring renamed files and filegroups, and using the REPLACE option.

See Also


Overview of Restore and Recovery in SQL Server

Other Resources

Implementing Restore Scenarios for SQL Server Databases

Help and Information

Getting SQL Server 2005 Assistance