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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-06-16 : 08:19:26
|
| Olive writes "Hi thereI have a rather complicated question. We are looking at putting a new server in to replace an older one, the only problem is that this older server is the publisher ( We have another server as the distributer ). We have simulated the enviroment in which we work and our test went as follows: We set the new and old servers up identical, we took the older one offline, copied the raw database files and logs ( the .MDF. LDF & .NDF including the master, tempdb and msdb database files ) to the new server, changed the new server's name to the old servers name( the old server is now off the network ). Booted it up and the replication took off from were it left on the new machine. This seems to have worked well, is there anything wrong with our "theory"? We didn't attach the database files on the new server, we copied and replaced it's database files in windows explorer and literally booted it up and it worked. Is there any long term affects that this has?If you can please let me know what you have to say, it would be greatly appriciated...Best Regards,Derrick" |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-06-16 : 13:58:33
|
| Well since it all worked for you, then there probably isn't a problem. Any problems that would have occurred would have already happened when you booted up the server or when replication started. Since everything is working, I would say that you server is in a stable state. You might want to run DBCC CHECKDB on all of the databases just in case though.Tara |
 |
|
|
|
|
|
Moving Replication to another server...