Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase «««123

Use Backup/Restore to Minimize Upgrade Downtimes Expand / Collapse
Posted Monday, June 22, 2009 9:37 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, February 11, 2011 1:42 PM
Points: 323, Visits: 42
nicely presented article, it is one of the best article on backup and restore topic which explained step by step process. thanks
Post #739512
Posted Monday, June 22, 2009 9:49 AM



Group: General Forum Members
Last Login: Friday, January 1, 2016 7:07 AM
Points: 1,688, Visits: 1,807
Robert Davis (6/18/2009)

I would like to say that the part below is not correct. A tail log backup is not a normal backup. to perform a tail log backup, you have to use the NoRecovery option on the backup log command. And when you do a tail log backup, it leaves the database in a restoring state so the database is not online any more. You don't have to take it offline.

Perform a final Transaction Log backup on the old server (this is called the tail log backup), and then take the database offline if it is a shared server


Thanks, I learned something new from this. Fundamentally they are doing the same thing if the application is not running and accessing the database, but you are correct that the more appropriate way of doing it would be to use the NORECOVERY option of BACKUP LOG (I didn't know this was there until I read your response and I'll have to go play with it in a bit).

Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Post #739530
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse