Quick Start

1) Run the application
2) Enter your server name in the "SQL Server" text box (servername\instance name) (do not include leading \\ on the server name)
3) Tick SQL Auth to use SQL Authentication, or leave for Windows authnetication (default)
5) Press Start to start collecting realtime data

Monitoring Clusters

To monitor a cluster, you should

1) Tick the Clustered check box
2) Enter the SQL Virtual Name or Virtual IP in the SQL Server text box
3) Enter the windows server name of the active node of the cluster, in the "Active Node" text box
4) Press Start to start collecting realtime data

Monitoring Disk Activity

By default, the application will display performance data for the C: drive. At any time you can change this by entering the drive letter (including the colon) in the disk storage text box, and then press the update button. You can also monitor the average data of all the drives by entering _Total (note the underscore) in the text box.

Detailed Views

The main form contains blue hyperlinks for some of the labels. These links will open a new dialog box with detailed information on the selected item. For performance reasons, some of these views will display a limited number of rows by default, but this can be changed by selecting a row count from the drop down menu.

Saving Detailed Data

All of the detailed view information can be dumped out to CSV by clicking the "save" button on the dialog box. This will create a single CSV file named after that view, with each row being date and time stamped. Multiple clicks of the save button will append the data (block seperated) to the same file. You can create your own graphical representations by opening that file in Excel.

Runtime Options


The options menu allows you to change the default alert thresholds for the main form, as well as enabling the logging options for the application. You can save the altered thresholds by clicking the save button. This will create a thresholhds.cfg file in the application folder. If present, this file will be appplied each time the application is run. You can only change these settings when the app is not monitoring SQL Server.

Blocked Process Monitoring

By ticking the Blocked Process option, SQL Live Monitor will log to CSV the SPID and input buffer of both blocked, and blocking processes - date and time stamped. Due to the additional checks and commands, there is a slight performance overhead by enabling this .... but only slight.

Capturing PAL Data

When ticking the PAL box in hte options menu, SQL Live Monitor will set-up the required perfmon counters (using logman) for analysis using PAL. The data collection will start when you press the start button, and will stop when you click the stop button. You can also change the sample interval and file format (csv by default).

Capturing data to CSV

In addition to displaying the performance data in realtime, you can tick the option to capture the info to CSV as well. Selecting this option will log all the main form data to a row date and time stamped CSV file, from which you can perform offline analysis or produce graphs using Excel. You can select this as well as the PAL option at the same time, which will give multiple monitoring points.

Saving Server Connections

Before you press the start button, you can press the save button, which will store the current SQL Server name, cluster settings, authentication mode, username and password (sql auth only) in an encrypted format. The file is called eServers.cfg and can be found in the application folder. Once a server is saved, the Saved Servers dropdown will display the server names, and you can switch by simply selecting a server from the list.

Remote Monitoring

SQL Live monitor is capable of monitoring a remote SQL server, as well as a local SQL Server. You need to ensure that the remote registry service can be contacted in order for the app to be able to connect properly. This feature can be very useful when monitoring from a central RDP server. If you are loggin into SQL Server using SQL Authentication, you have the option to specify alternate Windows Credentials, so that the tool can get required data from the remote registry. Remote Registry calls with Alternate credentials will use WMI.

Connection Driver

By default, the application will use the generic ODBC driver for SQL server. As of version 1.24, you can switch the driver to either the 2005 or 2008 SQL Native Client driver, by selecting the Driver option on the main form. For the most part, the default driver will be enough, however the ability to switch drivers may be required in some situations where the default driver is unable to connect.

Last edited Jun 17, 2014 at 7:00 AM by glensmall, version 11


nickm324 Mar 22, 2012 at 2:38 PM 
Tried two different servers and get the same error.

I have administrative access on both machines.

Any ideas what the issue is?

JamieCarroll Feb 18, 2010 at 3:43 PM 
I am unable to connect to a 2005 named instance either locally or remotely. Our setup is typically servername\instancename,nonstandardport on n-1 clusters. I've tried everything I can think of to connect both locally and remotely without success. Any insight would be appreciated.