upgrade from Windows server 2000 with sql server 2000 to Windows server 2003 Std with SQL server 2000 using the same name

I am replacing a server:  I have an old windows 2000 server running sql server 2000.  It is not a DC, no Exchange.  I am replacing it with a windows 2003 server std running sql server 2000.
I have 100 PCs connecting to the databases using ODBC.

I want to end up with the replacement server having the same name and ip address as the old one.  I want to have as little down time as possible.
I am hoping that once I get the new server on-line that the clients will see it and just work.
The server, database names, rights will be the same.

Is this going to work?
What is the best plan?

This is what I am planning:
After backing up and copying the databases off the old server.
Turn off the old server and delete it's computer account in the AD.
Name the new server to the same name as the old.
Join it to the domain.
Copy the database to the new server.
Attach the dabases with the same name.
Check the database rights.
Test.
Go on to the next project.

Thanks,

Bob C



 
RRCaldwellAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gary DewrellSenior Network AdministratorCommented:
Yes that works fine. Just did it not long ago.
I was a little more paranoid. My steps were:
1. Stage new server off network with same name and IP address.
2.Restore backup of DB's to new server.
3. Test that SQL could mount the DBs
4. Got happy becuse it actually worked
5. Stopped sql on old box
6. Got fresh copy of DBs copied to new box.
7. Disconnected NIC on old box
8. Removed account from AD
9. Connected new box to netwrok with correct IP
10. Joined to domain
11. Reboot
12. Said short prayer.

Whew! Go on to next project.

Might have missed a few minor steps and definately a few prayers in that list. :)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RRCaldwellAuthor Commented:
I will be doing this tomorrow night.

Thanks,

Bob C
0
Gary DewrellSenior Network AdministratorCommented:
How did it go Bob?
0
RRCaldwellAuthor Commented:
It did work.  Sorry I had not gotten back to you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.