Re: Moving databases to a new server

From: Tibor Karaszi (tibor_please.no.email_karaszi_at_hotmail.nomail.com)
Date: 04/18/04 

Date: Sun, 18 Apr 2004 22:31:04 +0200

Eddie,

I prefer backup/restore. But there are no hidden issues with detach and attach. Both methods will essentially
give you a binary copy of the database. As for the other things I recommend checking out some of the below
articles:

Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071

Moving Databases between Servers
http://www.support.microsoft.com/?id=314546

Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465

How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133

Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897

Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp

How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872

User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001

Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775 

-- 
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Eddie Stevens" <newsgroups@eddiestevens.com> wrote in message
news:VBAgc.220$Y52.98@newssvr32.news.prodigy.com...
>
> I am installing a new SQL server and need to move several databases from the
> old server. Both servers are running SQL 2000. I have read a number of
> Microsoft articles on this and they deal a lot with moving the master, and
> other system, databases. Do I need to move them too or can I just move the
> application databases? What is stored in Master, and other system databases,
> that I would need to copy?
>
>
>
> Also, there seem to be differing opinions as to the best way to move
> databases. Some recommend using the backup and restore functions while
> others favor detaching and attaching. I am leaning toward the detach and
> attach method but I want to make sure there are not any hidden problems with
> this method.
>
>
>
> I don't know if this will impact thee process, but he current server is a
> Windows 2000 server and the new server is running Windows Server 2003. The
> old server is also not updated to SP3a of SQL 2000. Do I need to upgrade the
> current server to the current service pack before I move the data? I am
> afraid that such an attempt might just push the current server over the
> edge.
>
>
>
> Eddie Stevens
>
>

Relevant Pages

  • Re: How to move system databases to new SAN drive in cluster serve
    ... I have moved model, msdb, and tempdb on a cluster ... Moving SQL Server databases to a new location with Detach/Attach ...
    (microsoft.public.sqlserver.clustering)
  • Re: Migrate stand alone sql server to a cluster without downtime
    ... Use backup and restore to create the databases on the new system. ... Run a log backup WITH STANDBY on each database on the old server. ... I support the Professional Association for SQL Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: SPS 2003 Portal change SQL server
    ... select portal site to delete and choose to NOT delete the databases ... server farm, you can just copy them over. ... attach the databases to the new sql server. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: AS2005 ... what is wrong with it?
    ... What I have seen is that the dev server is *faster* than the prod server ... And does your dev server also have all 6 databases with all these roles? ... When I restore the "PROV" i got approx 20 sec. ... Starting from an empty data folder should show if this theory is true ...
    (microsoft.public.sqlserver.olap)
  • RE: Moving SQL Server 2000 to a new machine
    ... In addition to all the CYA advise, you CAN move the system databases. ... Once you've got the new server at SQL2K, SP2, and the physical paths to ... > Recently I was tasked to move our entire SQL Server 2000 to a new server. ...
    (microsoft.public.sqlserver.server)
Loading