SQL Server Backup and Restore - Simple Talk

Chapter 6: Log Restores
You'll notice that in Listing 6-3 I added one minute to this time, the reason being that
the time output does not include seconds, and the transactions we want to include could
have committed at, for example, 2:33:45. By adding a minute to the output and rounding
up to 2:34:00, we will capture all the rows we want, but not the larger set of rows that
inserted next, after the delay. Note, of course, that the exact format of the timestamp, and
its actual value, will be different for you!
This time, we specify the RECOVERY parameter, so that when we execute the command
the database will enter recovery mode, and the database will be restored to the point of
the last committed transaction at the specified timestamp. When you run Listing 6-3 as a
whole, you should see output similar to that shown in Figure 6-8.
54 percent processed.
100 percent processed.
Processed 232 pages for database 'DatabaseForLogBackups_RestoreCopy', file
'DatabaseForLogBackups' on file 1.
Processed 5 pages for database 'DatabaseForLogBackups_RestoreCopy', file
'DatabaseForLogBackups_log' on file 1.
RESTORE DATABASE successfully processed 237 pages in 0.549 seconds (3.369 MB/sec).
100 percent processed.
Processed 0 pages for database 'DatabaseForLogBackups_RestoreCopy', file
'DatabaseForLogBackups' on file 1.
Processed 9 pages for database 'DatabaseForLogBackups_RestoreCopy', file
'DatabaseForLogBackups_log' on file 1.
RESTORE LOG successfully processed 9 pages in 0.007 seconds (9.556 MB/sec).
10 percent processed.
20 percent processed.
31 percent processed.
40 percent processed.
50 percent processed.
61 percent processed.
71 percent processed.
80 percent processed.
90 percent processed.
100 percent processed.
197