August 23, 2004 at 11:16 am
I've been handed a new Win2003 server with SQL 2000 SP3 and I need to move everything from a Win 2000 (SQL 2000 SP2) installation to the new machine. I have seen tutorials on moving when the OS is identical, but I can't find much info that applies to my situation. I need to move everything -- data, logins, DTS packages, maintenance plans, the whole shooting match.
What is the best way to approach this? I'm not necessarily interested in quick and easy (though that would be nice) but I want to do it right. We have lots of Web applications that make use of this server and I would like to keep downtime to a minimum. If anyone could point me at a good resource, I would appreciate it.
August 23, 2004 at 3:35 pm
I'd recommend to use Log Shipping to move database. I fliped to new sql server (over 20 databases (< 300G)) in 1 minitues.
This site has a lot of information about LogShipping I believe.
August 24, 2004 at 6:31 am
Thanks for the reply. I did some poking around looking for info on log shipping but didn't find much to help me actually set it up. It looks pretty complicated.
One thing I failed to mention is that we have the luxury of being able to take the existing server down for a couple of hours on the weekend if necessary. That being the case, why couldn't we just stop the existing server, copy the data files to the new server and then re-create the databases? I'm pretty sure that would work for the actual data, but what about logins, DTS packages, etc?
August 24, 2004 at 8:00 am
I would backup the DB's on the old machine, and then restore them on the new machine.
August 24, 2004 at 9:29 am
For logins,
you can use DTS package to move/copy logins to new server or you can follow this http://support.microsoft.com/default.aspx?kbid=246133
DTS package is easy, open the package and save as new server or file and if you save as file, copy the file to new server and open it and save as local from new box. Of course, you need to adust connections.
Jobs, script it and move it
Backup and Restore works really well if you can affort to have downtime. All depends on how big databases that you have.You still have to move login because you can't do backup and restore for systemdatabases since you have different service pack.
Just search the move database in this site, there a lot of discusses like this.
If you have Enterprise endition of SQL2K, you can use Wizard to do logShipping, it is quite easy.
August 24, 2004 at 9:29 am
For logins,
you can use DTS package to move/copy logins to new server or you can follow this http://support.microsoft.com/default.aspx?kbid=246133
DTS package is easy, open the package and save as new server or file and if you save as file, copy the file to new server and open it and save as local from new box. Of course, you need to adust connections.
Jobs, script it and move it
Backup and Restore works really well if you can affort to have downtime. All depends on how big databases that you have.You still have to move login because you can't do backup and restore for systemdatabases since you have different service pack.
Just search the move database in this site, there a lot of discusses like this.
If you have Enterprise endition of SQL2K, you can use Wizard to do logShipping, it is quite easy.
August 24, 2004 at 9:29 am
For logins,
you can use DTS package to move/copy logins to new server or you can follow this http://support.microsoft.com/default.aspx?kbid=246133
DTS package is easy, open the package and save as new server or file and if you save as file, copy the file to new server and open it and save as local from new box. Of course, you need to adust connections.
Jobs, script it and move it
Backup and Restore works really well if you can affort to have downtime. All depends on how big databases that you have.You still have to move login because you can't do backup and restore for systemdatabases since you have different service pack.
Just search the move database in this site, there a lot of discusses like this.
If you have Enterprise endition of SQL2K, you can use Wizard to do logShipping, it is quite easy.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply