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

Chapter 5: Configuration and Operation 73

However, with drag and drop, it is possible to move the primary for

VSQL2 to node2 and the backup to node1. Now neither of the Virtual

SQL Servers has a backup. Both node1 and node2 are primary for

Instance1 and cannot also act as a backup for another instance having the

same name.

Virtual SQL Servers

When you right-click on a Virtual SQL Server in the Name column, the

following options, described under “Other Procedures” on page 77, are

available:

• Delete – remove the Virtual SQL Server from the MxDB for SQL

Server configuration.

• Properties – modify the configuration of the Virtual SQL Server.

• Maintain – put the Virtual SQL Server in maintenance mode.

You can also do the following:

• Re-host the Virtual SQL Server. (See “Rehost a Virtual SQL Server” on

page 74.)

• Add a new virtual SQL instance. (See “Add a Virtual SQL Instance” on

page 59.)

•Install a new SQL instance.

Moving a Virtual SQL Server via “drag and drop” may leave the Virtual

SQL Server is a disabled state. Right-click on the Virtual SQL Server and

select “Enable on all servers” to re-enable it.

Node 2

Primary:

VSQL2, Instance1

Backup:

VSQL1, Instance1

Node 1

Primary:

VSQL1, Instance1

Backup:

VSQL2, Instance1

Node 3