Moving 5 databases to new server

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
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
> 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.
> parameters
> be migrated
> backup files
> logs also?
> 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 new server is 2000 version 8.00.760(SP3).
>
|||Some of below might help:
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
http://www.solidqualitylearning.com/
"scott" <scott@.discussions.microsoft.com> wrote in message
news:D4DB1784-FA39-4FD7-A9DC-F557759A333A@.microsoft.com...
> 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
|||also,...
Restore or Detach\Reattach will not move\migrate SQL Agent Jobs, System
Messages, DTS Packages, etc.
Greg Jackson
PDX, Oregon