3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 8: Upgrade Production SQL Servers 121

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 upgrade.

• If multiple SQL Service Monitors (vSQL Instances) share backup

nodes, the instances 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 will upgrade the version of the shared file DLLs. See

“Instance-Aware Components” on page 35 for more information.

• If you need to reboot the machine, all of the instances will be affected.

Upgrade Procedure

To perform the upgrade, complete these steps:

1. Move the Virtual SQL Server (VSQL) associated with the instance to

maintenance mode. Select the Virtual SQL Server on the PolyServe

Management Console, right-click, and select Maintain.

NOTE: Before placing the Virtual SQL Server into maintenance mode,

be sure that it is running on the primary node. This step

ensures that the virtual registry used by MxDB for SQL Server

will be updated properly.