SQL Server Backup and Restore - Simple Talk

Chapter 9: File and Filegroup Backup and Restore
keeps the database in a restoring state. The first half of the message output from running
this command, shown in Figure 9-6, tells us that the roll forward start point is at a specific
LSN number but that an additional roll forward is required and so more files will have to
be restored to bring the database back online.
The second part of the message simply reports that the restore of the backup for the
secondary data file was successful.
Since we specified that the database should be left in a restoring state after the second
restore command, SQL Server doesn't try to recover the database to a usable state (and is
unable to do so). If you check your Object Explorer in SSMS, you'll see that Database-
ForFileBackups is still in a restoring state.
After the full file backups, we took a transaction log backup (_TLOG), but since we're
rolling forward past the subsequent differential file backups, where any data changes
will be captured for each filegroup, we don't need to restore the first transaction log, on
this occasion. So, let's go ahead and restore the two differential file backups, as shown in
Listing 9-20.
USE master
GO
RESTORE DATABASE [DatabaseForFileBackups] FILE = N'DatabaseForFileBackups'
FROM DISK = N'C:\SQLBackups\Chapter9\DatabaseForFileBackups_FG1_Diff.bak'
WITH NORECOVERY
GO
RESTORE DATABASE [DatabaseForFileBackups] FILE = N'DatabaseForFileBackups_Data2'
FROM DISK = N'C:\SQLBackups\Chapter9\DatabaseForFileBackups_FG2_Diff.bak'
WITH NORECOVERY
GO
Listing 9-20: Restore the differential file backups.
324