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

Chapter 5: Configuration and Operation 82
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
Server will remain active on the original node and the status reported for
the monitor will be “UP Active (disabled).”
To disable a SQL service monitor, select it on the PolyServe Management
Console, right-click, and select Disable. To reenable the monitor, select it
on the Management Console, right-click, and select Enable.
Use the following commands to enable or disable the monitor from the
command line:
mx vsqlinstance enable <vsql\instance> <netif> ...
mx vsqlinstance disable <vsql\instance> <netif> ...
View Monitor Errors
To view the last error for a SQL service monitor, select the monitor on the
PolyServe Management Console, right-click, and select View Last Error.
Clear Monitor Errors
To clear an error, select the SQL service monitor where the error occurred,
right-click, and select Clear Last Error.
To clear an error from the command line, use this command:
mx vsqlinstance clear <vsql\instance> <netif> ...
Delete a Virtual SQL Instance
To remove a virtual SQL instance, select that instance on the Management
Console, right-click, and select Delete. During the delete, MxDB for SQL
Server removes the instance from the matrix and performs an operation
on the instance to return it to its original state. However, if this operation
fails, we recommend that you reinstall the instance.
NOTE: If the virtual SQL instance was associated with a Virtual SQL
Server that had been rehosted, the SQL instance will be unusable
after the virtual SQL instance is deleted. This situation occurs
because the rehost operation changes the SQL registry settings. If
you want to continue to use the SQL instance, you will need to
reinstall it.