Dell R810 - Manual (Page 23)

Servers: Database consolidation on Dell PowerEdge R810 servers
23
NOTE: If the time a full backup requires is unacceptable
given your migration maintenance schedule, you can take
the full backup at a previously scheduled time, and at this
point of the migration take only a differential or transaction
log backup. If the transaction log size is small relative to the
data file size, this approach can decrease migration time
significantly. If you go this route, however, be certain to
keep your backup chain intact.
Restoring your database to SQL Server 2008 R2 server
On the SQL Server 2008 R2 server, take the following steps:
1. Open SQL Server Management Studio, connect to
the SQL Server 2008 R2 instance, and restore
the database. (Restore times vary.) See
Appendix F for details.
NOTE: At this step, you must give your new database the
same name as your SQL Server 2000 database. Changing
the name could break applications that refer to the
database by name.
While in SQL Server Management Studio, reset the
database access property to multi-user, and set
the compatibility level to SQL 2008 (level 100).
See
Appendix F for details.
We show you how: After the move
After you have completed your side-by-side migration, you
typically will need to perform some post-migration tasks. Your
specific list of tasks will depend heavily on your pre-migration
research and planning. In this section, we briefly discuss a couple
of the most common tasks.
Logins and dependencies
Windows and SQL Server logins
As in past versions of SQL Server, there are two methods of
authenticating to SQL Server 2008 R2: Windows logins and SQL
Server logins. You create and administer Windows logins at the
Active Directory domain level, and you can assign those logins
rights to SQL Server resources. You create and manage SQL Server
logins, however, within SQL Server. The processes for extracting
login information and creating the transferred login entities on the
migration server is very similar for both Windows authenticated
logins and SQL Server authenticated logins. You should, however,