SQL Server Backup and Restore - Simple Talk

Chapter 6: Log Restores
restore and placed the database in a recovered state, ready for user access (with only ten
rows in each table!); no log backup files can then be applied as part of the current restore
operation. Always specify NORECOVERY if you need to continue further with a log backup
restore operation.
Of course, there are many other possible errors that can arise if you're not fully paying
attention during the restore process, and we can't cover them all. However, as one final
example, take a look at Listing 6-8 and see if you can spot the problem.
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',
NORECOVERY, STATS = 10, REPLACE
GO
RESTORE LOG [DatabaseForLogBackups]
FROM DISK = N'C:\SQLBackups\Chapter5\DatabaseForLogBackups_Native_Log_2.trn'
WITH FILE = 1, NORECOVERY, STATS = 10
GO
RESTORE LOG [DatabaseForLogBackups]
FROM DISK = N'C:\SQLBackups\Chapter5\DatabaseForLogBackups_Native_Log_1.trn'
WITH FILE = 1, RECOVERY, STATS = 10
GO
Listing 6-8: Forcing one more fun failure.
Did you catch the problem before you ran the script? If not, take a look at your output,
examine the error message you get when the first log file restore is attempted. I'm sure
you'll be able to figure out what's wrong in short order!
203