Use Backup/Restore to Minimize Upgrade Downtimes

  • daeguboog

    SSC Journeyman

    Points: 77

    Good article, very informative. You might want to spell check your article the next time you submit one. Justifiably or not, it can hurt your credibility if you submit an article with multiple spelling errors and typos to a professional forum. Just takes a second to run it through a spell checker.

  • Jonathan Kehayias

    One Orange Chip

    Points: 26778

    daeguboog (6/18/2009)


    Good article, very informative. You might want to spell check your article the next time you submit one. Justifiably or not, it can hurt your credibility if you submit an article with multiple spelling errors and typos to a professional forum. Just takes a second to run it through a spell checker.

    Perhaps you could point out the typo that you believe exists. This was written in Microsoft Word, and it passes a spell check, and manually reviewing it, there are no typos that I can find.

    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[/url]

  • Jonathan Kehayias

    One Orange Chip

    Points: 26778

    noeld (6/18/2009)


    Ermm... Isn't this just a description of LogShipping ?

    Yep, its basically manual log shipping. I've never used log shipping to accomplish this task because databases in my environment that I would be moving like this are already in FULL recovery. I generally off my existing backup set to perform all but the tail log restores. However, I have found in explaining this on the forums that people asking how to minimize down times, aren't in FULL recovery, and it is easier to explain how to manually do this, than to get them to setup log shipping to accomplish the same thing.

    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[/url]

  • Robert Davis

    One Orange Chip

    Points: 28027

    Jonathan Kehayias (6/18/2009)


    Perhaps you could point out the typo that you believe exists. This was written in Microsoft Word, and it passes a spell check, and manually reviewing it, there are no typos that I can find.

    I didn't notice any when I read it the first time, but I read it again after seeing the above posts, and there are several typos, but on the positive side, all of the typos are spelled correctly.

    top instead of to, to instead of too, its instead of it's. Nothing major, and I wouldn't have noticed if it hadn't been pointed out.

    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


    My blog: SQL Soldier[/url]
    SQL Server Best Practices:
    SQL Server Best Practices
    Twitter: @SQLSoldier
    My book: Pro SQL Server 2008 Mirroring[/url]
    Microsoft Certified Master: SQL Server, Data Platform MVP
    Database Engineer at BlueMountain Capital Management[/url]

  • Misha_SQL

    SSCertifiable

    Points: 5401

    Great approach. Thank you for the article!

  • honey_tnr

    Mr or Mrs. 500

    Points: 537

    nicely presented article, it is one of the best article on backup and restore topic which explained step by step process. thanks

  • Jonathan Kehayias

    One Orange Chip

    Points: 26778

    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

    Robert,

    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[/url]

Viewing 7 posts - 16 through 22 (of 22 total)

You must be logged in to reply to this topic. Login to reply