SQL Server 2000 Consolidation: a business case

3. Perform testing and monitoring during the critical period.
Start by preparing and completing a pre-go-live checklist. The table below represents a simple
checklist format. Another approach is to prepare the plan using Microsoft Project for better tracking of
time and resources.
Table 11. A simple go-live checklist format
SQL Server consolidation pre-go-live checklist
Item Steps Timing Resources Comments
Some recommended actions to include on the pre-go-live checklist are listed below. Consolidation
team members should include any additional checklist items, especially any new steps discovered
during the initial “pilot” consolidation.
• Select and schedule consolidation groups.
• Determine hardware and build requirements based on collected and analyzed data.
• Determine whether the required hardware is on hand or needs to be purchased.
• Secure existing hardware and/or order new hardware, allowing adequate time for delivery.
• Determine server build or upgrade requirements.
• Determine new server name, IP addresses, ports, instances, and cluster names.
• Establish new server network and application access plan (DNS, IP and FDQN, domains, accounts,
logins, application roles, linked servers, connection strings in applications, hard-coded logins in
stored procedures or jobs).
• Establish and publish the test and final cutover plan (dates, times, who is affected, trouble-reporting
procedure, rollback plan, etc.).
• Build or upgrade the server.
• Verify that virus protection is installed and has most recent virus definition files.
• Consolidating to a “swing” server (a new or clean upgraded server not currently part of the
development or production environment) is preferable to consolidating directly to a live server that
is currently in use.
• Document all servers involved in consolidation group:
– Generate script for entire database, including all objects, permissions, and dependencies. Store
in central location.
– Document all logins and passwords.
– Document linked servers, jobs, schedules, maintenance plan, backup modes and locations,
replication, log shipping, clustering, instance, and network settings.
– Document application. Include OLEDB connection strings and ODBC DSNs.
• Back up the data:
– Verify that the most recent database and log backups exist and were successful.
– Back up master and MSDB databases (to preserve descriptions of jobs, procedures, etc.)
– Make sure that backups (both data and logs) can be restored.
– The goal is to maximize recovery options. Secure data and log backup files, a copy of the
detached database, and a complete script of the entire database.
27