November 7, 2008 at 11:44 am
So, in a previous thread it was recommended to script out Logins, Jobs, Alerts & Notifications (what else ?) when migrating to new servers with new names. Not to try & restore MASTER.
There are 3 SQL2000 servers & 2 SQL2005 servers involved. The new servers will be the same version & build as the old servers.
How about MSDB & MODEL ? Can I do a restore of MSDB to the new server ?
November 7, 2008 at 12:09 pm
Are you moving sql 2000 db to sql 2005.
If so just do backup and restore....no need to do system databases they are different in SQL 2005.
Just go get the sp_help_revlogin script and exec this on sql 2000 that give you your logins.
November 7, 2008 at 12:25 pm
The restore of msdb will take care of jobs and I believe you alerts as sysalerts resides there.
The procedure that Tracey mentioned will allow you to script out the logins and passwords. You can use the sp_change_users_login. I believe there is more information here - http://www.sqlservercentral.com/articles/Log+Shipping/63028/
Hope this helps.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
November 7, 2008 at 12:48 pm
TRACEY (11/7/2008)
Are you moving sql 2000 db to sql 2005.If so just do backup and restore....no need to do system databases they are different in SQL 2005.
Just go get the sp_help_revlogin script and exec this on sql 2000 that give you your logins.
Sorry for the confusion.
The SQL2000 sp4 databases are going to new boxes (w/ new names) with new installation of SQL2000 sp4.
The SQL2005 sp2 databases are going to new boxes (w/ new names) with new installation of SQL2005 sp2
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply