Moving SQL Server

Here's my situation. I have a production SQL server 2000 with 18 databases
that's lease is up and i need to move everything to the new server and keep
the ip address and the computer name the same because of how some of the
databases are written. My approach will be to join the domain with the new
server under a different ip and pc name, get everything installed, tested,
then take the old server down and change the ip and pc name on the new server
to what the old server was. Does anyone know any guidelines i should follow
with this or step by step instructions for doing this? Also, the old server
is running win2k the new server will be running win2k3. Will there be any
problems with this?
TIAYou shouldn't have any IP problems...
The only thing you have to do on the new server is
sp_dropserver origservername
go
sp_addserver newservername, local
This is assuming you have no SQL replication set up..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:05395E91-3BB4-4F5C-B7BB-3F92EF7552FF@.microsoft.com...
> Here's my situation. I have a production SQL server 2000 with 18
databases
> that's lease is up and i need to move everything to the new server and
keep
> the ip address and the computer name the same because of how some of the
> databases are written. My approach will be to join the domain with the
new
> server under a different ip and pc name, get everything installed, tested,
> then take the old server down and change the ip and pc name on the new
server
> to what the old server was. Does anyone know any guidelines i should
follow
> with this or step by step instructions for doing this? Also, the old
server
> is running win2k the new server will be running win2k3. Will there be any
> problems with this?
> TIA|||Hi
See the following to rename the server:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp
If you install the same version/patches then I can't think of any problems.
You may want to create your own network that you can test out the server and
applications before make it live. This would also allow a trial run.
John
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:05395E91-3BB4-4F5C-B7BB-3F92EF7552FF@.microsoft.com...
> Here's my situation. I have a production SQL server 2000 with 18
databases
> that's lease is up and i need to move everything to the new server and
keep
> the ip address and the computer name the same because of how some of the
> databases are written. My approach will be to join the domain with the
new
> server under a different ip and pc name, get everything installed, tested,
> then take the old server down and change the ip and pc name on the new
server
> to what the old server was. Does anyone know any guidelines i should
follow
> with this or step by step instructions for doing this? Also, the old
server
> is running win2k the new server will be running win2k3. Will there be any
> problems with this?
> TIA|||Well, it depends on how the domain you are on is setup. Is it running
Active Directory? Is it Windows 2000/2003? Are you using WINS? The
easiest thing to do when you switch the servers is generally to rename the
old server and assign a different IP address. You then want to restart it.
You can then bring up the new machine with the different name and IP
address. When this is done make sure the name and IP address you were using
for the new machine is no longer in use by DNS or WINS. If it is after the
synchronization time, go into DNS and WINS is you have it (which sucks if
you do) and tombstone or delete the old entries.
"dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
news:05395E91-3BB4-4F5C-B7BB-3F92EF7552FF@.microsoft.com...
> Here's my situation. I have a production SQL server 2000 with 18
databases
> that's lease is up and i need to move everything to the new server and
keep
> the ip address and the computer name the same because of how some of the
> databases are written. My approach will be to join the domain with the
new
> server under a different ip and pc name, get everything installed, tested,
> then take the old server down and change the ip and pc name on the new
server
> to what the old server was. Does anyone know any guidelines i should
follow
> with this or step by step instructions for doing this? Also, the old
server
> is running win2k the new server will be running win2k3. Will there be any
> problems with this?
> TIA|||we are currently running active directory with windows 2003. We use DNS and
WINS right now because there are still some nt40 servers being used.
Thanks to everyone for all the help
"Derrick Leggett" wrote:
> Well, it depends on how the domain you are on is setup. Is it running
> Active Directory? Is it Windows 2000/2003? Are you using WINS? The
> easiest thing to do when you switch the servers is generally to rename the
> old server and assign a different IP address. You then want to restart it.
> You can then bring up the new machine with the different name and IP
> address. When this is done make sure the name and IP address you were using
> for the new machine is no longer in use by DNS or WINS. If it is after the
> synchronization time, go into DNS and WINS is you have it (which sucks if
> you do) and tombstone or delete the old entries.
> "dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
> news:05395E91-3BB4-4F5C-B7BB-3F92EF7552FF@.microsoft.com...
> > Here's my situation. I have a production SQL server 2000 with 18
> databases
> > that's lease is up and i need to move everything to the new server and
> keep
> > the ip address and the computer name the same because of how some of the
> > databases are written. My approach will be to join the domain with the
> new
> > server under a different ip and pc name, get everything installed, tested,
> > then take the old server down and change the ip and pc name on the new
> server
> > to what the old server was. Does anyone know any guidelines i should
> follow
> > with this or step by step instructions for doing this? Also, the old
> server
> > is running win2k the new server will be running win2k3. Will there be any
> > problems with this?
> >
> > TIA
>
>