
23
Migrating to a Dell PowerEdge R515 server from two legacy database servers
3. 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 G for details.
4. Modify application connection strings or change Domain Name
System (DNS) pointers that reference the migrated database.
WE SHOW YOU HOW: AFTER THE MOVE
After you have completed your side-by-side migration, you typically
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 several of the most common tasks.
Logins and dependencies
Windows and SQL Server logins
As in previous 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 either the
operating system level or 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 and SQL Server-authenticated logins. You should,
however, take some extra steps to ensure a smooth migration for SQL
Server logins.
Below, we describe how to script both Windows-authenticated logins
and SQL Server-authenticated logins to a query window and recreate
them on the new SQL Server 2008 R2 virtual machine.
Please see Appendix H for details on transferring Windows logins and
Appendix I for details on transferring SQL Server logins.
Comentarios a estos manuales