Dell PowerEdge R810 Manual page 24

With intel xeon processor l7555 database consolidation
Hide thumbs Also See for PowerEdge R810:
Table of Contents

Advertisement

Servers: Database consolidation on Dell PowerEdge R810 servers
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 server. Step 6
refers solely to the SQL Server login type.
Please see
Appendix G
and
Appendix H
for details on transferring SQL Server logins.
To transfer logins, take the following steps on the SQL Server 2008
R2 server. Note that steps 1 through 5 apply to both Windows
logins and SQL Server logins.
1.
In SQL Server Management Studio, in the Object
Explorer pane, connect to both your SQL Server
2000 server and your SQL Server 2008 R2
server. Be sure to have the Object Explorer
Details tab open (View | Object Explorer Details).
2.
Expand the tree view of the SQL Server 2000
server, browse to the security tab, and click the
logins node. In the Object Explorer Details, you
will now see a list of all logins on the SQL Server
2000 server.
3.
If necessary, use the sorting and filtering options
in the Object Explorer Details tab, and take note
of which logins you would like to migrate. Select
them by clicking; use the standard Windows
controls (Ctrl key, Shift key, etc.) to select
multiple logins.
4.
Right-click the logins you selected, and choose
Script Login As | Create To | New Query Window.
Be sure to change the connection of this query
window to connect to your new SQL Server 2008
R2 server, if it is not doing so already, by right-
clicking and selecting Change Connection.
5.
Execute the script on your SQL Server 2008 R2
server to create the logins. If you are transferring
Windows-based logins, the process is complete.
If you are transferring SQL Server logins,
continue with Step 6 below.
6.
For SQL Server logins, the script you executed in
Step 5 creates the login, marks it as disabled,
and assigns it a random password, but the script
does not map the login to the database user. To
avoid having a database user that is ―orphaned‖
from a login, use the sp_change_users_login
for details on transferring Windows logins
24

Advertisement

Table of Contents
loading

Table of Contents