Re: best method for switching to a new server
- From: "John Richardson" <j3richarson@xxxxxxxxx>
- Date: Tue, 20 Dec 2005 14:49:25 -0800
thanks for the references. I will go over them when I get the chance.
I can get the moving the db thing, no prob, but it's the in between part
where it's moved and all the clients are still talking to the old db...
I have a lot of reading to do. :)
"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message
news:exCaHOaBGHA.3496@xxxxxxxxxxxxxxxxxxxxxxx
> John,
>
> You will have to interrupt the clients at some point in time to switch
> them over. Detaching and attaching the db is probably the fastest way to
> move the actual db. All of that can be scripted, even the move with
> xp_cmdshell. Here are some articles that may help with the move. Just
> make sure you have good and tested backups before you start anything.
>
>
> http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
> http://www.databasejournal.com/features/mssql/article.php/3379901
> Moving system DB's
> http://www.support.microsoft.com/?id=314546 Moving DB's between
> Servers
> http://www.support.microsoft.com/?id=224071 Moving SQL Server
> Databases to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465 Using WITH MOVE in a
> Restore
> http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
> Moving Users
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
> a Restore
> http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 User Logon and/or
> Permission Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 How to Resolve Permission
> Issues When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
> Restoring a .mdf
> http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
> for SQL Server
>
> --
> Andrew J. Kelly SQL MVP
>
>
> "John Richardson" <j3richarson@xxxxxxxxx> wrote in message
> news:%23mzcR6ZBGHA.3064@xxxxxxxxxxxxxxxxxxxxxxx
>> 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.
>>
>
>
.
- References:
- best method for switching to a new server
- From: John Richardson
- Re: best method for switching to a new server
- From: Andrew J. Kelly
- best method for switching to a new server
- Prev by Date: Re: best method for switching to a new server
- Next by Date: RE: SQL Server Setup could not validate the service accounts
- Previous by thread: Re: best method for switching to a new server
- Next by thread: Re: upgrade from 2000 to 2005
- Index(es):
Relevant Pages
|
