Consolidating multiple SQL Server systems onto
Dell PowerEdge R610 Servers using Microsoft’s Hyper-V
30
g. Are there any non-default master or model
database objects?
h. Are there any linked server objects?
i. Are other SQL modules involved or dependent
on this instance (e.g., Analysis Services,
Reporting Services, etc.)?
j. Default installation directories, data
directories, and log directories
k. Tempdb – Is it highly volatile? Slightly volatile?
Medium usage?
4. Database level
a. Database properties and options
b. Recovery model, auto-shrink, etc.
c. Files and filegroups
i. Size
ii. Location
5. Backups
a. How many full backups, and on what
schedule?
b. How many differential backups, and on what
schedule?
c. How many log backups, and on what
schedule?
d. Current backup window?
e. Can backup window shift to accommodate
the consolidated backup window?
f. Other backup issues
6. Other issues
a. Is this database in a replication
configuration?
b. Do any SQL Server Integration Services
(2005/2008)/Data Transformation Services
(2000) packages reference this database?
c. Do any SQL Agent jobs reference this
database?
7. Users/Logins
a. Number of users this database affects
b. Would this database require a login whose
name conflicts with another name on the
target consolidation server? If so, you would
need to create the login and map the
database user using
sp_change_users_login.
Komentarze do niniejszej Instrukcji