HP StorageWorks Storage Mirroring application notes (T5437-96014, December 2009)

Figure 3 SQL server replication results
.
10. The master and msdb database objects related to the databases moved must be moved manually
to the SQL Server 2008 instance, including logins, jobs, and alerts.
11. Either change the target identity to match the SQL 2005 server, then restart the target (so that
clients can connect using the original server identity), or redirect clients and applications to the
new SQL 2008 server.
If you change the target name to the source name but retain the original IP on the target, then
DNS entries may need to be updated.
How the testing solution works
1. A new SQL 2008 server is built on new or existing hardware.
2. Storage Mirroring is installed on both the existing SQL 2005 server (source) and the new SQL
2008 server (target).
3. A replication set is created to replicate the SQL databases and logs from the SQL Server 2005
source server to the SQL Server 2008 target server. However, unlike a typical Storage Mirroring
high availability scenario, the SQL 2008 services on the target are left running.
4. Disconnect the replication set between the source and target.
5. Attach the databases to the SQL Server 2008 target using SSMS or sqlcmd with a SQL command
file.
6. Verify that the databases attached successfully.
7. The master and msdb database objects related to the databases moved must be moved manually
to the SQL Server 2008 instance, including logins, jobs, and alerts.
8. (Optional) Reconfigure client to attach to target to test.
6