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.
| Author |
Topic |
|
homebrew
Posting Yak Master
114 Posts |
 Posted - 2006-04-27 : 15:05:06
|
| We're moving to a new server, and I was thinking I could detach the DBs since they are on separate storage, then reattach after the new server recognizes the storage array. But I remembered that you can't detach a DB if it's being replicated. What other options are there ? Regular backup & restore (several additional hours) ?Also, should I configure the new server as a Publisher & Distributor, then restore the Distribution DB from the old server to the new server along with the other systems DBs ?SQL2000 SP3, Win 2000 (old server) to Win2003 (new server) |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-04-27 : 15:07:35
|
| If you are going to keep the same paths, then you can simply stop the MSSQLSERVER service on both servers, copy the mdfs and ldfs over to the new server, including the ones for the system databases, then start the MSSQLSERVER service on the new server. Using this method means you don't have to copy over logins, jobs, DTS packages, etc... manually.As long as the paths are the same, you shouldn't run into problems. I've done this several times. Never with replication running, but it might work. Hopefully you have a test box to test this out.Tara Kizeraka tduggan |
 |
|
|
|
|
|
|
|
Moving SQL to a new Server (w/ replication)