May 13, 2009 at 3:02 am
HI.
First of all you should know that I've very little experience(about 1-2 years) and I hope I fit the right Category for this topic.
My Question is how should I move the SQL Server to the new hardware(SQL Server version is the same and the filestructure ist also the same).
preliminary work:
-> New Server ist installed(same SQL Server 2000 with SP4; same filestructure, same collation)
General Information:
-> I have got about 2 hours window to move the Databases to the new Server(no writes to the original server in this window)
-> The original Server includes Replication with another Server and DTS-Jobs(Packages could be copied to the new Server but how?)
Task List:
1) I'm starting to remove the replication
2) Backup all Databases(including Systemdatabases)
3) Stop SQL Server service and SQL Agent Service on original Server
4) Restore Userdatabase on new Server
x)How can transfer the Logins to the new Server???Check orphaned users ....
x)How can I copy the DTS-Jobs to the new Server???
n)rename de Server to original Name. Does the SQL Server rename(it is a Default Instance no Named Instance)?
n+1)install Replication and Test
Does anything miss in my Tasklist or is something wrong to move to the new Hardware? Would be detach/attach better?
Thank you very much for your help.
Yours Frank
May 13, 2009 at 8:04 am
kiendl.franz (5/13/2009)
HI.First of all you should know that I've very little experience(about 1-2 years) and I hope I fit the right Category for this topic.
My Question is how should I move the SQL Server to the new hardware(SQL Server version is the same and the filestructure ist also the same).
preliminary work:
-> New Server ist installed(same SQL Server 2000 with SP4; same filestructure, same collation)
General Information:
-> I have got about 2 hours window to move the Databases to the new Server(no writes to the original server in this window)
-> The original Server includes Replication with another Server and DTS-Jobs(Packages could be copied to the new Server but how?)
Task List:
1) I'm starting to remove the replication
2) Backup all Databases(including Systemdatabases)
3) Stop SQL Server service and SQL Agent Service on original Server
4) Restore Userdatabase on new Server
x)How can transfer the Logins to the new Server???Check orphaned users ....
x)How can I copy the DTS-Jobs to the new Server???
n)rename de Server to original Name. Does the SQL Server rename(it is a Default Instance no Named Instance)?
n+1)install Replication and Test
Does anything miss in my Tasklist or is something wrong to move to the new Hardware? Would be detach/attach better?
Thank you very much for your help.
Yours Frank
Generally speaking I would say your list ok, though depending on the size of your databases I'm not sure if you can manage it within 2 hours. I usually use detach/atach because in most cases it's faster than making backups and restore them. Best thing is to do a test restore so you know how much time it will take.
About migrating Logins see here: http://support.microsoft.com/kb/918992
The DTS packages you can save as .dts file and then import into your new seerver. The jobs you can script by using the generate script option in EM.
When renaming the new server you have to update the sysservers table. See here http://www.sqlservercentral.com/articles/Administration/65/ on how to do it.
Hope this helps
[font="Verdana"]Markus Bohse[/font]
May 13, 2009 at 9:28 am
Thank you very much Markus Bohse.
This information helps me very much.
The link for the transfer of the Logins shows a solution for SQL Server 2005. I found a solution who shows the transport via DTS(Login transfer). Have you ever done so?
I will try to detach and attach I think this would be much faster as you said.
Wish you a nice day.
Yours Frank
May 13, 2009 at 11:39 am
May 13, 2009 at 12:50 pm
Here is an easier way for DTS package moves (I'm currently doing the same here). Open the DTS package and simply do a package->save as and change the server name to your new server. It doesn't have to be a linked server but I'm willing to bet it has to be on the same domain. The one pain is you have to do it package by package - unless I've missed something, which is entirely possible! 😀
-- You can't be late until you show up.
May 13, 2009 at 1:04 pm
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply