3.6.0 Matrix Server Upgrade Guide (5697-7085, February 2008)

Chapter 4: Non-Rolling Upgrades 26

Upgrade Considerations for SQL Server 2005

If you will be upgrading SQL Server 2000 instances to SQL Server 2005,

you should be aware of the following:

• Before upgrading a SQL Server 2000 instance, remove the

corresponding Virtual SQL Instance from the Virtual SQL Server. (On

the PolyServe Management Console, right-click on the Virtual SQL

Instance and select Delete.) After the instance is upgraded, you can

recreate the Virtual SQL Instance.

• A Virtual SQL 2005 instance cannot be a backup for a Virtual SQL 2000

instance having the same name (and vice versa). A Virtual SQL

Instance and all of its backups must be running the same version of

SQL Server.

Upgrade Procedures

There are two procedures:

• Upgrade Matrix Server and reinstall the operating system. See page

26.

• Upgrade Matrix Server without reinstalling the operating system. See

page 30.

Upgrade Matrix Server and Reinstall the OS

To minimize overall downtime, divide your servers into two groups and

then upgrade one group at a time while the other group runs the matrix.

The upgrade procedure assumes that the servers are divided into group

A and group B.

If you prefer to upgrade all servers at once, be sure to take the following

steps to retain the matrix configuration:

• Leave one server running the old operating system and matrix

software. You can shut down the other servers as indicated below.

• After the first server is upgraded to the new operating system and

matrix software, restore the matrix configuration directory from

backup.