best method for switching to a new server
- From: "John Richardson" <j3richarson@xxxxxxxxx>
- Date: Tue, 20 Dec 2005 11:52:56 -0800
My (small) company just upgraded their server from 2k to 2003 Bus Ed.. We
are currently running both computers on the network, but we now want to move
the Sql Server 2K database from the old to the new. I'm a little nervous
about it, cause the database is the backbone of the company.
So the question is how do I make the transition as error proof and seamless
as possible?
There are about 10 clients each pointing to the old server, and I'm doing
this all remotely (from a different city), so it will be difficult to just
detach and attach the database to the new one; this would break all the
clients.
I've been toying with the idea of setting up replication first, and testing
out the new server first before making an official switch, but I have no
experience with setting up replication, and don't even know if this is a
good idea. This must be a common scenario, so what is the best route for me
to go to minimize downtime?
Thanks.
.
- Follow-Ups:
- Re: best method for switching to a new server
- From: Andrew J. Kelly
- Re: best method for switching to a new server
- From: Geoff N. Hiten
- Re: best method for switching to a new server
- Prev by Date: SQL2k on Windows 2003 - in workgroup?
- Next by Date: Re: best method for switching to a new server
- Previous by thread: SQL2k on Windows 2003 - in workgroup?
- Next by thread: Re: best method for switching to a new server
- Index(es):
Relevant Pages
|