Required Full Backup

Restoring a database to a point in time or to the point of failure requires a specific restore sequence that begins with the last Full Database backup performed prior to that point. Any Differential, Partial or Transaction Log backups performed after the Full Backup are restored next, to roll the database forward. After you perform certain database managerial tasks, you must perform a new Full Database backup to re-establish the restore sequence. If you perform a Database Differential, Transaction Log, Partial Database or File and FileGroups backup after performing one of these tasks, a Full Database backup performed prior to performing the task may no longer work to successfully restore the database.

To ensure a successful database restore, always perform a Full Database backup immediately after you have performed any of the following actions:

• Created a new database
• Changed the recovery model of the database
• Changed the number of files or FileGroups in the database
• Changed the arrangement of files among the FileGroups
• Changed the arrangement of tables among the FileGroups
• Changed the partition scheme of a Partitioned Table or Index
• Canceled a full backup job while it is running
• Modified the database definition, including adding or removing a table, or changing the definition of a table
• Added or removed an index
• Restored the database from backups