RE: Moving 5 databases to new server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Scott (Scott_at_discussions.microsoft.com)
Date: 06/22/04 

Date: Tue, 22 Jun 2004 12:20:01 -0700

I am placing the production database in single user mode to ensure there are no other users.

I have actually performed the restores and they worked OK. I am not restoring the system databases only user databases.

The link you provided did not work.

"DeeJay Puar" wrote:

> Hi,
>
> Here are some comments:
>
> 1. Production server does have to in 'Single User Mode',
> since no one is going to be connected.
>
> 2. If you do a fullbackup and restore without further
> activity on the database, you do not have to restore any
> transaction log backups.
>
> 3. I do not think, restores will work with different
> service packs (production is different level than new
> server).
>
> 4. Here is an nice article to review:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;314546&Product=sql
>
> hth
>
> DeeJay
> >-----Original Message-----
> >In a few hours I am going to move 5 user databases from
> the existing production server to a new one. I have a
> plan in place, but I would like to verify that its the
> correct approach.
> >Here's my plan:
> >
> >1. Stop SQL Server on production using Services Manager
> >2. Start SQL Server on production in Single User Mode
> > -using Services Manager, type "-m" in startup
> parameters
> >3. Perform a manual Full Backup of each user database to
> be migrated
> >4. Stop the SQL Server on production
> >5. Restore each database on the new server from the
> backup files
> > -check "force restore over existing database"
> >6. Link all orphaned logins on each database
> >7. Point the application to the new server
> >
> >My main question is: Do I need to restore transaction
> logs also?
> >
> >No users will be connected at the time of the full
> backup. I am currectly using the Full recovery model on
> each database. I have already recreated all the DTS jobs
> and Database Maintenance Plans on the new server. The new
> server is not yet in use, so I was able to test the
> process by restoring each database from the production
> backup files to the new server.
> >
> >The production SQL Server is 2000 version 8.00.194(RTM).
> The new server is 2000 version 8.00.760(SP3).
> >
> >Am I overlooking anything?
> >
> >Thanks,
> >
> >Scott
> >.
> >
>

Relevant Pages

  • Re: Problem with disable msde connection pool
    ... 'ALTER DATABASE TestDB SET single_user WITH ROLLBACK after 10 ... ' Restart the server... ... ' Execute query through SQLDMO to run the restore TSQL command ... the connection pool must be disabled. ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Restore public folders and companyweb
    ... I understand that the Public Folder Store ... > database cannot be mounted due to integrity problems, ... > the pub.edb database from your backup of the old Server, ... please try the following steps to restore your public ...
    (microsoft.public.windows.server.sbs)
  • Re: Best Way for restoring AD in a test lab
    ... Well do a backup and restore following most of the procedures outlined. ... Just do a backup on a production dc. ... > DC to the test lab with the same Server Name and this is our DR process. ... >> Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Re: test environment windows 2003
    ... an authorative restore after the demote and system state restore. ... This document was prepared for the building of a copy of the production ... Remove the physical cable for the new pc and build the member server ... Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Re: SQL 2000 SP4 on 2003 Server - Single User Mode
    ... I found the section where you list the filename to restore to. ... rename the SQL Server the same as what is listed below Courthouse? ... Once you've created your database (simply right click on the Database ...
    (microsoft.public.sqlserver.setup)