November 17, 2002 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/sjones/movingmsdb.asp
November 21, 2002 at 6:25 am
Hi steve, good article.
Other things to watch:
a) if moving msdb and model at the same time, attach model before msdb. I have run it issues with database ID's being mixed up (though rare).
b) if moving to new servers, you may need to re-schedule jobs and may find yourself editing the syspackages table to fix up the originating server column. Not Nice but effective.
Cheers
Chris K
Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
November 21, 2002 at 1:51 pm
Very very true. Be sure that if you move servers, the target server issue may crop up as well.
See my kill that target article for details.
Steve Jones
November 25, 2002 at 7:26 am
Very good article...
madhusudannaidugundapaneni
Madhu
November 25, 2002 at 9:45 am
November 28, 2002 at 1:41 am
Good and very useful article. But I just want to add a link to another article in case something goes wrong with sp_attach.
http://www.sqlteam.com/item.asp?ItemID=10060
Everybody should read this one before moving system databases. It gives you some very interesting insights into how SQL Server uses them.
[font="Verdana"]Markus Bohse[/font]
December 2, 2002 at 10:03 am
Intersting link and I agree. Definitely worth the read.
Steve Jones
July 19, 2005 at 11:10 am
Very useful article. I've solved my problem.
Alexander Mai
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply