SQL Server Backup and Restore - Simple Talk

Chapter 8: Database Backup and Restore with SQL Backup Pro
Rerun our data verification query, from Listing 8-18 and you should see that we now have
the 42 rows restored to MessageTable2.
Restore to standby using a SQL Backup script
Before we move on, it's worth taking a more detailed look at the SQL Backup T-SQL
script that we'd use to perform the same point-in-time restore operation.
EXECUTE master..sqlbackup '-SQL "RESTORE DATABASE [DatabaseForSQLBackups_Standby]
FROM DISK = ''C:\SQLBackups\Chapter8\DatabaseForSQLBackups_Full_BASE2.sqb''
WITH NORECOVERY, MOVE ''DatabaseForSQLBackups''
TO ''C:\SQLData\DatabaseForSQLBackups_Standby.mdf'',
MOVE ''DatabaseForSQLBackups_log'' TO
''C:\SQLData\DatabaseForSQLBackups_Standby_log.ldf''"'
EXECUTE master..sqlbackup '-SQL "RESTORE LOG [DatabaseForSQLBackups_Standby]
FROM DISK = ''C:\SQLBackups\Chapter8\DatabaseForSQLBackups_Log_3.sqb''
WITH STANDBY = ''C:\SQLBackups\Undo_DatabaseForSQLBackups_Standby.dat'',
STOPAT = ''2011-12-06T10:42:46'', ORPHAN_CHECK"'
Listing 8-19: Restore to standby SQL Backup script.
The first command restores the base backup file to a new database, using the MOVE
argument to copy the existing data and log files to the newly designated files. We
specify NORECOVERY so that the database remains in a restoring state, to receive
further backup files.
The second command applies the log backup file to this new database. Notice the use of
the WITH STANDBY clause, which indicates the restored state of the new database, and
associates it with the correct undo file. Also, we use the STOPAT clause, with which you
should be familiar from Chapter 4, to specify the exact point in time to which we wish
to roll forward. Any transactions that were uncommitted at the time will be rolled back
during the restore.
288