SQL Server Performance Forum – Threads Archive

Replace production server

We are going to replace our production old server with new one. About two weeks ago, I setup the new server by detach/attach the system and user databases on the new server. Also, forced the new server#%92s name to the SQL-Server. Then Testers test the applications and everything was fine.
In coming weekend I am going to replace the servers. Here is the plan:
1.Get backup from all user databases
2.Move the BAK files into new server
3.Replace the old box by new box
4.Restore BAK files on the new server
By using this approach, do I miss something?
The new server will have new name but same IP. We didn#%92t have any table update or DTS/Job change. Do you think it is better to use detach/attach approach again? Is there any risk involved?
CanadaDBA

---

If there is a server name change then you must workout to change the jobs or dTS packages that are involved with old server name. I would suggest this linkhttp://vyaskn.tripod.com/moving_sql_server.htm by vyas which is comprehensive to maintain the implementation without any hassle. The detach/attach approach is easier than using BACKUP/RESTORE statements. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

---

Thank you my knowledgeable guru. Also, thanks for the link. As usual good and effective!

CanadaDBA

---

]]>