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

Chapter 5: Configuration and Operation 61

• The SQL instance cannot be in use on any of the nodes as a

primary for another Virtual SQL Server.

• The SQL instance on the primary node cannot currently be a

backup for another Virtual SQL Server.

Port: For SQL Server 2000, this field lists the port that you specified when

you installed the SQL instance. For SQL Server 2005, enter the port

number for TCP/IP Sockets that the SQL Server instance should listen on.

Specifying a port is required for SQL Server 2005.

Virtual data root: Specify the full path that will be used for the data files

and directories for this virtual SQL Server instance. This location will

store the SQL Data Root that was created when the SQL Server instance

was installed. (In mx commands, the virtual data root is referred to as the

vpath.)

Master data file, Master log file, Error log file: These fields display the

locations of the database and log files.

Optional Components: When you add a SQL instance to a Virtual SQL

Server, MxDB for SQL Server also creates a service monitor. This monitor

periodically checks the health of the SQL service for this instance. If the

service monitor detects that its check has failed, by default the

ClusterPulse process (provided with Matrix Server) will fail over the

Virtual SQL Server to a backup node. (You can use the Advanced options

to customize this behavior.)

NOTE: A failure of the SQL Agent will not trigger a failover of the Virtual

SQL Server.

When the service monitor detects that the SQL service is down, MxDB for

SQL Server can try to restart the service instead of immediately failing

over the Virtual SQL Server. The optional component “SQL Service

Restart Attempts” allows you to specify the number of attempts that

should be made. If you do not specify a number for this component, the

Virtual SQL Server will fail over to a backup node.

Probe Configuration: The SQL monitor periodically probes the health of

the SQL Server service on the node where the Virtual SQL Server is

active. The frequency is the interval of time, in seconds, at which the