SQL Server Backup and Restore - Simple Talk

Chapter 6: Log Restores
DatabaseForLogBackups_RestoreCopy database, which is a FULL recovery model
database, and we have not backed up the tail of the log, so we would lose any transactions
that were not previously captured in a backup.
This is a very useful warning message to get in cases where we needed to perform crash
recovery and had, in fact, forgotten to do a tail log backup. In such cases, we could start
the restore process with the tail log backup, as shown in Listing 6-6, and then proceed.
USE master
GO
BACKUP LOG DatabaseForLogBackups_RestoreCopy
TO DISK = 'D:\SQLBackups\Chapter5\DatabaseForLogBackups_RestoreCopy_log_tail.trn'
WITH NORECOVERY
Listing 6-6: Perform a tail log backup.
In cases where we're certain that our restore operation does not require a tail log backup,
we can use WITH REPLACE or WITH STOPAT. In this case, the error can be removed,
without backing up the tail of the log, by adding the WITH REPLACE clause to Listing 6-5.
Let's take a look at a second example failure. Examine the script in Listing 6-7 and see if
you can spot the problem.
--STEP 1: Restore the log backup
USE [master]
GO
RESTORE DATABASE [DatabaseForLogBackups_RestoreCopy]
FROM DISK = N'C:\SQLBackups\Chapter5\DatabaseForLogBackups_Native_Full.bak'
WITH FILE = 1,
MOVE N'DatabaseForLogBackups'
TO N'C:\SQLData\DatabaseForLogBackups_RestoreCopy.mdf',
MOVE N'DatabaseForLogBackups_log'
TO N'C:\SQLData\DatabaseForLogBackups__RestoreCopy_1.ldf',
STATS = 10, REPLACE
GO
201