4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

6. Confirm the upgrade
If the upgrade was successful, check the SQL error logs and event logs for any errors.
Also check basic database access by connecting with the Query Analyzer and
querying one of the databases.If the upgrade failed, return the machine to the exact
machine state before the upgrade. To do this, perform a restore using your backup
files.
7. Notify users of upgrade completion
When the upgrade is complete, notify users that they can resume their regular
database activities.
8. Back up the machine state
Back up the new machine state and create a base line.
Upgrade SQL instances
Be sure to apply the procedure to your test system before upgrading a production
machine.
Upgrade considerations
When performing an upgrade, you should be aware of the following:
• Because the upgrade is done per instance, it should be repeated for each instance.
Microsoft supports a machine running SQL instances with different versions.
• Rolling upgrades are not supported. You cannot access the database while the
upgrade is running.
• Upgrades need to be performed during change management windows. Therefore,
you should restrict access to the database to avoid corruption caused by the up-
grade.
• If multiple SQL Service Monitors (vSQL Instances) share backup nodes, the in-
stances will be disabled during maintenance mode. These instances will need to
be enabled during the upgrade process as noted below.
• On a machine with multiple SQL Server 2005 instances, running the first upgrade
may upgrade the version of the shared file DLLs. See “Instance-Aware compon-
ents” on page 63, for more information.
Upgrade production SQL Servers154