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

Post-upgrade recommendations
The following procedures should be performed after the upgrade is complete.
Update statistics
To ensure optimal performance of an upgraded database, Microsoft recommends running
SP_UPDATESTATS (update statistics) against the upgraded database on the SQL Server 2008 server.
Updating statistics using SP_UPDATESTATS is described in more detail in the SQL Server 2008
documentation at http://msdn.microsoft.com/en-us/library/ms187348.aspx.
Update counts
It is only necessary to run DBCC UPDATEUSAGE once after upgrading from SQL Server 2005. See
SQL Server 2008 Books Online for more information at http://msdn.microsoft.com/en-us/library/
ms188414.aspx.
Change compatibility mode
When SQL 2005 databases are attached to a SQL 2008 server, their compatibility mode is set to
90. Administrators may need to set the database compatibility level to 100. See SQL Server 2008
Books Online for more information at http://msdn.microsoft.com/en-us/library/bb510680.aspx.
Move login permissions
There are many possible variations for how client permissions can be moved to the new SQL 2008
database. Due to the large number of possible configurations, instructions for how to configure client
connections are out of the scope of this document.
Configure client connectivity
After the databases are attached to the SQL 2008 server, you may remove the source server from
the network, change the network name and IP address of the target server to those of the source, and
reboot (other DNS changes may also be necessary). Clients should now be able to reconnect to the
SQL 2008 server just as they did previously.
Another option would be to configure clients and applications to use the new target server. Configuring
users and clients in this manner is beyond the scope of this document.
12