Adding servers to monitor

SQL Monitor - 2.0

Versions available: 3.2, 3.1, 3.0, 2.3, 2.2, 2.1, 2.0

Learning SQL Monitor - 2.0

Adding servers to monitor

Once you have installed SQL Monitor and created the login password, choose the SQL Servers you want to monitor.

Go to the Configuration tab and under Monitoring, select Monitored servers.
Click the Add SQL Server to monitor button. The Add SQL Server panel is expanded:
Enter the fully qualified name of the instance you want to monitor in the SQL Server box, including any subdomains. You can type the first few characters of a server name to display matching suggestions.
To add a cluster, enter the name of any node in the cluster. Click for more information about accepted formats.
You will need to provide two sets of credentials:
- to connect to the host Windows machine on which the instance is running
- to connect to the SQL Server instance
By default SQL Monitor uses the Base Monitor Service account for both sets of credentials. This is the Windows account you specified during installation to connect to the Data Repository (the SQL Server database that stores all collected data). You can specify a different account to use to connect to the host Windows machine and to the SQL Server instance.

For more information, see "Monitoring SQL Servers" in Account permissions required by SQL Monitor.
To set more advanced properties, for example, to connect to a SQL on a different port, click Edit properties to display the Connection properties box:

Enter the properties you want to change for this instance, then click OK. If you change the connection properties, they are identified as Custom:

Note that the connection properties are persisted until you move to a different page in SQL Monitor. If you add more servers, they will use the custom connection properties.
When you click Add, the host machine and instance(s) are both added to the list of monitored servers below the Add SQL Server to monitor panel.

Once added, server names cannot be edited. If you have typed the name incorrectly, the server will be added with a status of "Connection failed (Unreachable)". You will need to remove the server, and then add it again.

The Status column indicates whether SQL Monitor has successfully connected to the server and its instances:

Status	Definition
Monitoring (Connected)	Connection was successful; monitoring data is being collected.
Monitoring stopped (Incorrect credentials or insufficient permissions)	SQL Monitor cannot connect to the host machine or instance. Check that the credentials supplied to log in to the host machine are valid and have sufficient permissions to collect WMI data, read the registry, and access files. For more information, see Account permissions required by SQL Monitor.
Connection failed (Unreachable)	Host machine does not exist or is offline, or one of the required services (WMI, Remote Registry) is not started. Check that you have entered the name correctly, and that your machine is not behind a firewall.
Connection failed (Internal SQL Monitor error)	Unknown application error; please contact Red Gate support with information about your error.
Connection failed (Bad data)	SQL Monitor cannot process some data collected from the host machine. The performance counter library may be corrupt and needs rebuilding, or a required registry key may not exist. For information about rebuilding your PerfMon library, see http://support.microsoft.com/kb/300956. Click Show log and refer to the Exception and Exception message columns in the table of data collection events to determine the specific problem.
Connection failed (Cannot connect)	SQL Monitor cannot connect to the host machine for reasons other than credentials authorization. Click Show log and refer to the Exception and Exception message columns in the table of data collection events for information about the type of problem.
Unlicensed	Your evaluation period has expired and the machine has not yet been licensed.
Suspended	Monitoring on this machine or instance has been manually suspended.

Monitoring stopped or Connection failed status

If the status is Monitoring stopped (Incorrect credentials or insufficient permissions), do one of the following:

Edit the credentials specified in SQL Monitor. Move your mouse pointer over the row for the server and click Edit credentials. SQL Monitor will automatically retry the connection using the updated credentials.
Go to the host machine or SQL Server instance and edit the login permissions for the supplied account. When you have edited the credentials, go back to SQL Monitor, click in the row for that server and select Retry connection.
If the status is Connection failed, click Show log and refer to the Exception and Exception message columns in the table of data collection events:

Note: For Connection failed status, SQL Monitor will automatically retry the connection every few seconds.