November 1, 2012 at 8:02 am
does anyone know if the NO_TRUNCATE option still works in sql 2012?
or should the CONTINUE_AFTER_ERROR option be used instead_
November 1, 2012 at 8:13 am
Yes, the option is still valid in 2012: http://msdn.microsoft.com/en-us/library/ms186865.aspx. It is equivalient to using both COPY_ONLY and CONTINUE_AFTER_ERROR.
NO_TRUNCATE
Specifies that the log not be truncated and causes the Database Engine to attempt the backup regardless of the state of the database. Consequently, a backup taken with NO_TRUNCATE might have incomplete metadata. This option allows backing up the log in situations where the database is damaged.
The NO_TRUNCATE option of BACKUP LOG is equivalent to specifying both COPY_ONLY and CONTINUE_AFTER_ERROR.
November 1, 2012 at 8:17 am
ok just tried it and NO_TRUNCATE seems to work fine so far
November 1, 2012 at 8:30 am
Two ways to take a tail log backup.
1) The DB is online and usable and you want to backup the last of the transactions before starting a restore/moving the DB/etc
- BACKUP LOG ... WITH NORECOVERY
2) The DB is unavailable and damaged and you want to salvage as much as you can from the tran log before starting a restore
- BACKUP LOG ... WITH NO_TRUNCATE
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply