SQL Server Backup and Restore - Simple Talk

Chapter 8: Database Backup and Restore with SQL Backup Pro
Execute the script, then, while it is running, we can take a quick look at the SQL Backup
monitoring stored procedure, sqbstatus, a feature that lets us monitor any SQL Backup
restore operation, while it is in progress. Quickly open a second tab in SSMS and execute
Listing 8-14.
EXEC master..sqbstatus
GO
Listing 8-14: Red Gate SQL Backup Pro monitoring stored procedure.
The stored procedure returns four columns: the name of the database being restored; the
identity of the user running the restore; how many bytes of data have been processed;
and the number of compressed bytes that have been produced in the backup file. It can
be useful to check this output during a long-running restore the first time you perform
it, to gauge compression rates, or to get an estimate of completion time for restores and
backups on older versions of SQL Server, where Dynamic Management Views are not
available to tell you that information.
Once the restore completes, you'll see restore metrics similar to those shown in Figure
8-21, but with an additional section for the tail log restore. If you rerun Listing 8-12 to
verify your data, you should find that the "missing" 21 rows in MessageTable2 are back!
SQL Backup point-in-time restore to standby
In our final restore example, we're going to restore a standby copy of the DatabaseFor-
SQLBackups database to a specific point in time in order to attempt to retrieve some
accidentally deleted data.
Standby servers are commonly used as a High Availability solution; we have a secondary,
or standby, server that can be brought online quickly in the event of a failure of the
primary server. We can restore a database to the standby server, and then successively
279