3.4.3 MxDB for SQL Server Installation and Administration Guide

Chapter 3: Configuration and Operation 48
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
The SQL instance must exist on all of the nodes providing
network interfaces for the Virtual SQL Server. (The instance
must have the same name on all of the nodes.)
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.
Database File, Log File, Error Log: These fields display the locations of
the database and log files.
Optional Component. 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 timeout is the maximum amount of time that will be waited
for the probe to complete. The default timeout interval is 15 seconds.