3.6.0 Matrix Server Command Reference (5697-7083, December 2007)

Chapter 3: mx Commands 120

This option enables transactions that span one or more Virtual SQL Servers.

However, the following limitations exist when using a Virtual SQL Server

with MSDTC:

• Because only one MSDTC resource exists per machine, you can define

MSDTC support for only one Virtual SQL Server per machine. You can,

however, define other Virtual SQL Servers that do not support MSDTC.

• If two MSDTC-enabled Virtual SQL Servers share the same backup and

both Virtual SQL Servers fail, the first server to come up will lock the

MSDTC resource, preventing the other Virtual SQL Server from starting.

• You cannot use COM+ components or MSMQ on a node where MSDTC

has been virtualized.

For more information about MSDTC, see the MxDB for SQL Server

Administration Guide.

<ip> is the IP address for the SQL Virtual Server. <name> is the NetBIOS name

for this Virtual SQL Server; the name can include up to 15 characters.

The order in which you specify the network interfaces determines the

ordering for failover. The first network interface is the primary interface;

network traffic for the Virtual SQL Server goes to the node providing this

interface. The remaining network interfaces are backups. Each network

interface must be located on a different node.

delete—Delete a Virtual SQL Server

mx vsql delete <vsql>

disable—Disable a Virtual SQL Server

mx vsql disable <vsql>

dump—Dump the Virtual SQL Server configuration to stdout

mx vsql dump

enable—Enable a Virtual SQL Server

mx vsql enable <vsql>

maintain—Place a Virtual SQL Server in maintenance mode

mx vsql maintain <vsql>