July 2, 2013 at 10:30 pm
when do we take tail-log backup? and how can we take? wt cmds to be used
July 3, 2013 at 1:08 am
When your database is damaged and you are trying to do a last-ditch backup of the log before starting restoring over it, or when for other reasons you're restoring or moving a DB and want to ensure that no transactions are lost.
It's a backup log command. WITH NO_TRUNCATE if the log is damaged, with NO_RECOVERY if it's not.
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
July 3, 2013 at 12:07 pm
thankyou
July 3, 2013 at 1:42 pm
you would use the norecovery option on a log backup when you want to swap primary and secondary roles in a logshipping set up without needing to reinitialise from a full backup.
---------------------------------------------------------------------
July 3, 2013 at 3:09 pm
manikanta1207 (7/2/2013)
when do we take tail-log backup? and how can we take? wt cmds to be used
This sounds like a series of interview questions. My recommendation is that Gail's good answer has given you the end result but you need to readup about backups and TailLog backups in Books Online. Just in case you don't know what "Books Online" is, open SSMS then press the {f1} key and you're there (is the SQL Server "help" system).
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply