Replace 2000 server running SQL 2000 with new 2003 standard running SQL 2005. These are NOT Domain Controllers

1. Build 2003 server and install SQL 2005 and any other apps (e.g. virus scanner, inventory apps, Dell Openmanager, etc...)
2. Change the IP of the W2k SQL server so clients don't connect and change the data while you are migrating it.
3. Give the 2003 server a different IP as well (we don't want users connecting to this server untill the data is fully migrated)
4. Do a full backup of the databases on the 2000 server and restore them to the 2003 server.
5. Ensure all Jobs, Stored Procedures, Users are moved and setup correctly on the new server.
6. Connect to the databases with every application that uses this server and test key functions (if this is a mission critical app you should test all funcitons)
7. Change the IP of the 2003 server to match the original IP of the 2000 server and away you go!
8. Don't forget to setup the backup on your new server

How would you go about a name change I want the new 2003 server to have the same name of the original old 2000 server.

Well you have 2 options.

1. At step 7 change the name of the 2003 server to match the name of the 2000 server (take 2000 server offline permanantly or change it's name first)
2. Allow the 2003 server to have a new name and create an alias in DNS with the 2000 server's name and point it at the new name of the 2003 server.

My suggestion is to do this in DNS rather than changing the server's name.  I've run into issues in the past when I build a new server and name it the same as an old server.

I'm increasing the points, I need to make sure I don't forget anything.
 
New Server has all software installed and ready to go. have not moved data yet. can't take old server offline untill after hours. I will backup SQL database to a USB drive, and plug it into the new server and use the restore feature pointing to the USB drive for restoring. maybe there's a better way of doing this my SQL file is 1.5 gig.

1) Old Server 2000  name is Let's say ( prodution.local ip= 10.11.0.230) connected to domain PRESS

2) New Server 2003 name is 1212superior and is still in a workgroup. IP address is whatever the dhcp server sent it will be changing this to staic anyways.

3)Do I have to first disjoin the domain on old server (production)  and put it into a workgroup before shutting it down? or do I connect the new server 2003 into the domain with the current name 1212superior and dynamic ip.

Thanks

I would get all the data off the old server (backup to USB Key or Network Share), change it's name, disjoin it from the domain, and change it's IP before shutting it down.  (This way if someone accidentaly turns it back on you won't create a conflict)

Then I would change the new server to 10.11.0.230 and change it's name to the old server's name.  Restart the box and join it to the domain.

You will probably want to have both servers online so you can easily check to make sure all your stored procedures, jobs, databases, indexes, etc... were properly moved to the new server.  The key here is to change the IP and name of the old server before backing up the data.  This is what will prevent users from connecting and modifying the data after you backed it up.  You could take it offline but then you won't be able to connect to it yourself with Enterprise Manager.

Got it:

Last question.

I will be the only one connecting to the servers, it's going to be done tommorrow so I have all weekend incase I run into problems. This server is also running IIS untill next week when I bring up a new server dedicated to web services. So I don't beleive I can have both servrers online at the same time. I guess I can turn off IIS on old server before bring new server online.

1) If I can't get it working can I alway reverse what we did above, or would that cause problems?

Thank You for your expertise.

No more questions.

best

Mike