Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 best way to move a SQL Server Instance

Author  Topic 

jpotucek
Constraint Violating Yak Guru

273 Posts

Posted - 2008-04-02 : 13:19:03

We have a SQL Server 2000 ent edition sp4 Named Instance with 3 small databases and one 4 GB database which is REPLICATED

The Server has been bouncing like a yoyo today because of a disk controller problem and I am preparing to move the Instance to a whole new server this afternoon. The new Server will have the same IP and name as the original server. Any suggestions for the easiest or most seamless way to make this happen? Backup and Restore, detach attach, replace mdf and ldf files, ... any suggestions would be appreciated.

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-04-02 : 13:26:58
Check this out for 2000
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=99534 id="Book Antiqua">
Go to Top of Page

jpotucek
Constraint Violating Yak Guru

273 Posts

Posted - 2008-04-02 : 14:18:48
basically our old server has crashed and all I have is a full set of backups.. Should I recover system DBS and THEN user DBS? how about replication. when should I restore the Distribution DB?
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-04-02 : 14:24:15
Did you check the link I have provided? It explains clearly what you looking for. Recovering user DBs will be enough but you have to synchronize logins and jobs .
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-04-02 : 14:25:46
Oops! If your system has already crashed,then you have to migrate System DB as well.Check the link.
Go to Top of Page

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2008-04-02 : 14:35:04
The simplest answer is restore system DBs and then user DBs. It'll bring over all logins and keep the synced up with the users. If the server name and IP are the same as the one that crashed, you should be fine with this approach. We did this very thing this weekend, though by choice, and not a system crash. Not a single issue came up.

Terry
Go to Top of Page

jpotucek
Constraint Violating Yak Guru

273 Posts

Posted - 2008-04-02 : 15:16:31
is the process the same for restoring Systgem DBs in 2000 as it is in 2005??? I have docs on 2005. Also, do I restore the Distributor DB for replication?
Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-04-02 : 15:45:57
Are you moving instances from SQL 2000 to 2005? Am i right?
Go to Top of Page

jpotucek
Constraint Violating Yak Guru

273 Posts

Posted - 2008-04-02 : 16:36:57
2000 to 2000 They built a server with the same OS, IP and Name as the dead server.

Go to Top of Page

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-04-02 : 16:39:49
How did you old server crash? Then you should be good in migrating system databases as well but not from SQL 2000 to 2005.
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-04-02 : 22:09:06
The way to restore system db is same as in sql2k5, and should restore distribution db as well.
Go to Top of Page

jpotucek
Constraint Violating Yak Guru

273 Posts

Posted - 2008-04-03 : 10:48:22
Thanks very much!!! I did restore all system DBs, Distribution, User (replicated) database and then recreated publication from script .. all came up fine.
Go to Top of Page
   

- Advertisement -