Share this page

# SQL Server monitor

The SQL Server monitor shows the measurements and server properties that can be monitored on the SQL database server during the test run.

In this topic:

## Set up the SQL Server monitor

This task describes how to set up the SQL Server monitor.

To set up the monitor:

1. Prerequisites.

   If your monitor accesses a server outside of your internal network, you may need to set up a web proxy to collect data from it. For details, see Use a proxy server.

2. Select a resources folder for the monitor profile in the resources tree, or create a new folder as follows:

   1. Click the Navigation menu and select Assets > Monitors.

   2. Click the New Folder button and enter a name for the monitor resources folder.

3. Create a monitor profile.

   1. Click the New Monitor Profile button , and make sure Monitor Profile is selected.

   2. Enter a name and optional description for the monitor profile, and click Save. An empty monitor profile is added to the selected resources folder.

   3. Select the monitor profile you just added and click the Add Monitor button .

   1. In the Monitor Type Selection tab, select the SQL Server monitor type and click Next.

   2. In the Monitor Definition tab, enter the server details:

      UI Elements | Description
      --- | ---
      Server | The name or IP address of the server whose resources you want to monitor.
      User Name | The monitored server's user name, if relevant.
      Password | The monitored server's password, if relevant.

   3. Click Get Counters to display a list of available metrics and counters.

      Select the measurements that you want to monitor, and then click to add the counters to the Selected Counters table.

      The following table describes the default counters that can be monitored on version 6.5 of the SQL Server.

      Measurement | Description
      --- | ---
      % Total Processor Time | The average percentage of time that all the processors on the system are busy running non-idle threads. On a multi-processor system, if all processors are always busy, this is 100%, if all processors are 50% busy this is 50% and if 1/4 of the processors are 100% busy this is 25%. It can be viewed as the fraction of the time spent doing useful work. Each processor is assigned an Idle thread in the Idle process which consumes those unproductive processor cycles not used by any other threads.
      % Processor Time | The percentage of time that the processor is running a non-idle thread. This counter was designed as a primary indicator of processor activity. It is calculated by measuring the time that the processor spends running the thread of the idle process in each sample interval, and subtracting that value from 100%. (Each processor has an idle thread which consumes cycles when no other threads are ready to run). It can be viewed as the percentage of the sample interval spent doing useful work. This counter displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time the service was inactive, and then subtracting that value from 100%.
      Cache Hit Ratio | The percentage of time that a requested data page was found in the data cache (instead of being read from disk).
      I/O - Batch Writes/sec | The number of 2K pages written to disk per second, using Batch I/O. The checkpoint thread is the primary user of Batch I/O.
      I/O - Lazy Writes/sec | The number of 2K pages flushed to disk per second by the Lazy Writer.
      I/O - Outstanding Reads | The number of physical reads pending.
      I/O - Outstanding Writes | The number of physical writes pending.
      I/O - Page Reads/sec | The number of physical page reads per second.
      I/O - Transactions/sec | The number of Transact-SQL command batches run per second.
      User Connections | The number of open user connections.

   4. Click Save. The monitor details are displayed in the Monitors tab for the selected monitor profile.

4. Associate the monitor with your test.

   For details, see Step 3: Associate monitors with your test.

Back to top

## Notes and limitations

If you encounter a "Failed to retrieve measurements" error when trying to get monitor counters or run a test, see Monitor fails to retrieve measurements.

Back to top

See also:

- Monitors

https://admhelp.microfocus.com Enterprise Performance Engineering,LoadRunner Enterprise 8942
Tips to improve your search results...OpenText™ Enterprise Performance Engineering Help Center OpenText™ Enterprise Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: