<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Jonathan Kehayias
»
Use Backup/Restore to Minimize Upgrade...
22 posts, Page 2 of 3
««
1
2
3
»»
Use Backup/Restore to Minimize Upgrade Downtimes
Rate Topic
Display Mode
Topic Options
Author
Message
SanjayAttray
SanjayAttray
Posted Thursday, June 18, 2009 8:14 AM
Hall of Fame
Group: General Forum Members
Last Login: Friday, March 15, 2013 2:43 PM
Points: 3,924,
Visits: 1,554
noeld (6/18/2009)
Ermm... Isn't this just a description of LogShipping ?
Yep. it is.
SQL DBA.
Post #737585
Adam Haines
Adam Haines
Posted Thursday, June 18, 2009 3:26 PM
SSCrazy
Group: General Forum Members
Last Login: 2 days ago @ 9:39 PM
Points: 2,278,
Visits: 2,998
Good job Jonathan :)
My blog:
http://jahaines.blogspot.com
Post #737949
Ronzo
Ronzo
Posted Thursday, June 18, 2009 3:58 PM
Mr or Mrs. 500
Group: General Forum Members
Last Login: 2 days ago @ 2:06 PM
Points: 502,
Visits: 511
I'd probably add a step at the end.
After the applications are up and you're sure they're all pointed at the new server and working fine, bring the old database back on-line (or restart the old SQL Server), and perform a final full backup. This is useful for ensuring you have a copy of the database as it existed in its old environment at the time of cutover. As you noted, sometimes the new database may not be restorable on the old server (different SQL versions). And depending on auditing requirements, you may need a restorable backup for off-site storage. It also gives you a picture of the data as it existed at the point of cutover.
Have Fun!
Ronzo
Post #737969
Cameron Mayfield
Cameron Mayfield
Posted Thursday, June 18, 2009 4:00 PM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, August 04, 2010 1:08 PM
Points: 3,
Visits: 55
Very good information. Thank you for sharing.
Post #737971
Robert Davis
Robert Davis
Posted Thursday, June 18, 2009 4:55 PM
SSCommitted
Group: General Forum Members
Last Login: Sunday, May 19, 2013 8:09 AM
Points: 1,558,
Visits: 1,396
If you are upgrading SQL 2005 to SQL 2008 or an earlier version of SQL 2005 to a newer version (such as SP1 to SP3), then you can do this with database mirroring. Then you don't need to do the tail backup or any of the manual steps when it comes time to switchover. You just need to perform a failover.
Best part is, you can update the client conenction strings ahead of time to have the new server as the principal and the old server as the mirror and the client will automatically switch to the new machine.
And if you want, you could then upgrade the old server and keep using it as a mirror for the new server.
My blog: SQL Soldier
Twitter:
@SQLSoldier
Microsoft Certified Master: SQL Server 2008
Sr. Product Consultant and Chief SQL Server Evangelist @ Idera
My book: Pro SQL Server 2008 Mirroring
Post #737983
daeguboog
daeguboog
Posted Thursday, June 18, 2009 7:07 PM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, June 24, 2009 11:48 PM
Points: 1,
Visits: 17
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.
Post #738008
Jonathan Kehayias
Jonathan Kehayias
Posted Thursday, June 18, 2009 9:04 PM
SSCommitted
Group: General Forum Members
Last Login: Sunday, May 12, 2013 4:26 PM
Points: 1,696,
Visits: 1,742
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
Post #738027
Jonathan Kehayias
Jonathan Kehayias
Posted Thursday, June 18, 2009 9:17 PM
SSCommitted
Group: General Forum Members
Last Login: Sunday, May 12, 2013 4:26 PM
Points: 1,696,
Visits: 1,742
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
Post #738029
Robert Davis
Robert Davis
Posted Thursday, June 18, 2009 11:24 PM
SSCommitted
Group: General Forum Members
Last Login: Sunday, May 19, 2013 8:09 AM
Points: 1,558,
Visits: 1,396
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
Twitter:
@SQLSoldier
Microsoft Certified Master: SQL Server 2008
Sr. Product Consultant and Chief SQL Server Evangelist @ Idera
My book: Pro SQL Server 2008 Mirroring
Post #738057
mishaluba
mishaluba
Posted Saturday, June 20, 2009 3:10 PM
Mr or Mrs. 500
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 5:54 PM
Points: 525,
Visits: 617
Great approach. Thank you for the article!
Post #738911
« Prev Topic
|
Next Topic »
22 posts, Page 2 of 3
««
1
2
3
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
