Move System BD's?

I am getting ready to move SQL server from a failing server to a new one. It
houses Great Plains and SQL 2000. I want to move the system databases also.
I am having a hard time finding the correct KB article to tell me how to
move the system databases. Can someone point me in the right direction?
Thanks
I suspect these are what youa re after:
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scri...p?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues
Andrew J. Kelly SQL MVP
"Steve Gould" <steve.gould(at)apawood.org> wrote in message
news:eSeIYzV4EHA.4092@.TK2MSFTNGP14.phx.gbl...
>I am getting ready to move SQL server from a failing server to a new one.
>It houses Great Plains and SQL 2000. I want to move the system databases
>also.
> I am having a hard time finding the correct KB article to tell me how to
> move the system databases. Can someone point me in the right direction?
> Thanks
>
|||Which system databases specifically are you referring to?
You cannot move the master database. Tempdb would be a worthless exercise
to move.
You can backup the model and restore it as well as the msdb database,
however with a new ServerName, you may have some issues with jobs performing
properly from the msdb database.
Replication will be a problem if you are using it.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Steve Gould" <steve.gould(at)apawood.org> wrote in message
news:eSeIYzV4EHA.4092@.TK2MSFTNGP14.phx.gbl...
>I am getting ready to move SQL server from a failing server to a new one.
>It houses Great Plains and SQL 2000. I want to move the system databases
>also.
> I am having a hard time finding the correct KB article to tell me how to
> move the system databases. Can someone point me in the right direction?
> Thanks
>
|||The only issue with moving the master database is that you install the same
Version and Edition and Service Pack and Hotfix level. After that, you can
move the old master in place of the new one. Be careful that the SQL Server
service accounts have login privleges to the old master before you bring it
offline. After the old one is on the new server, execute the sp_dropserver
sp_addserver with local parameter so the old master knows which host it now
resides on.
Again, the biggest challenge for jobs and the use of the old msdb database
is one of permission and the SQL Server service accounts.
Sincerely,
Anthony Thomas

"Rick Sawtell" <quickening@.msn.com> wrote in message
news:%233nfhHW4EHA.3416@.TK2MSFTNGP09.phx.gbl...
Which system databases specifically are you referring to?
You cannot move the master database. Tempdb would be a worthless exercise
to move.
You can backup the model and restore it as well as the msdb database,
however with a new ServerName, you may have some issues with jobs performing
properly from the msdb database.
Replication will be a problem if you are using it.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
"Steve Gould" <steve.gould(at)apawood.org> wrote in message
news:eSeIYzV4EHA.4092@.TK2MSFTNGP14.phx.gbl...
>I am getting ready to move SQL server from a failing server to a new one.
>It houses Great Plains and SQL 2000. I want to move the system databases
>also.
> I am having a hard time finding the correct KB article to tell me how to
> move the system databases. Can someone point me in the right direction?
> Thanks
>
|||Thank you for that update. I think I am not going to try it. I am a total
SQL novice. We hired a consulting company to install and set up SQL server
and GreatPlains for us and now we are regretting our limited involvement. My
boss is also regretting not having spent the money to send me to SQL server
classes when we had the time. Now we pay the price. I found an article
targeted at moving GreatPlains and it covers all the steps to move the
databases and fix the login issues. I am going to use it as my check list
and hope all works out OK. I am also getting a consultant on standby just in
case.
Thanks for all the help guys!
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23PMiIJY4EHA.664@.TK2MSFTNGP10.phx.gbl...
> The only issue with moving the master database is that you install the
> same
> Version and Edition and Service Pack and Hotfix level. After that, you
> can
> move the old master in place of the new one. Be careful that the SQL
> Server
> service accounts have login privleges to the old master before you bring
> it
> offline. After the old one is on the new server, execute the
> sp_dropserver
> sp_addserver with local parameter so the old master knows which host it
> now
> resides on.
> Again, the biggest challenge for jobs and the use of the old msdb database
> is one of permission and the SQL Server service accounts.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Rick Sawtell" <quickening@.msn.com> wrote in message
> news:%233nfhHW4EHA.3416@.TK2MSFTNGP09.phx.gbl...
> Which system databases specifically are you referring to?
> You cannot move the master database. Tempdb would be a worthless exercise
> to move.
> You can backup the model and restore it as well as the msdb database,
> however with a new ServerName, you may have some issues with jobs
> performing
> properly from the msdb database.
> Replication will be a problem if you are using it.
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
> "Steve Gould" <steve.gould(at)apawood.org> wrote in message
> news:eSeIYzV4EHA.4092@.TK2MSFTNGP14.phx.gbl...
>