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

Caveats and special considerations
• If the user-created database(s) you are trying to migrate already exist on the target (for example,
if there is a duplicate name because of a previous test), you must detach, delete, or otherwise get
rid of that target database. Otherwise, you will need to replicate the source copy to a unique
location and attach the database using a different name.
• You must use the same account for all detach/attach operations because a permissions discrepancy
between the SQL, operating system, domain, and NTFS permissions may cause the process to
fail. If the permissions are not consistent, you may receive an "access denied" error when attempting
to attach the database.
Sample implementation
This section describes how this solution has been implemented to use Storage Mirroring to assist with
a migration from SQL Server 2005 to SQL Server 2008.
NOTE:
Because no two environments or configurations are exactly the same, you will need to modify the sample
implementation in order to make the solution work in your environment.
Requirements
For this solution, your system must meet the following requirements.
Source server
• Microsoft® Windows® Server® 2003 with the most recent service pack, or Windows Server
2008 with service pack 1 or later
• Storage Mirroring with the most recent service pack
• SQL Server 2005
Target server
• Microsoft Windows Server 2003 with the most recent service pack, or Windows Server 2008
with service pack 1 or later
• Storage Mirroring with the most recent service pack
• SQL Server 2008 with the most recent service pack
Install software on the source
1. Install Storage Mirroring on the source server using the installation defaults. See the HP Storage-
Works Storage Mirroring User’s Guide for details.
HP StorageWorks Storage Mirroring application notes 7