LoadRunner Monitoring SQL Server

When monitoring SQL Server, you can add metrics. However, only system resource-related metrics have data, and SQL Server-related metrics have no data.

Workaround:

Instead of adding SQL Server counters in system Resource graphs by adding Windows resources, you can add an object that is Sqlserver:general Statistics, and the counter is selected by the user Connections

What SQL Server performance metrics should I collect?
It is generally necessary to monitor the following indicators:

1) SQL Server resource monitoring in indicator Cache CTR (Cache hit Ratio), the higher the value the better. If it lasts below 80%, you should consider increasing the memory.

2) If the full scans/sec (whole table Scan/sec) counter displays a value that is higher than 1 or 2, you should analyze your query to determine whether full table scanning is really required, and whether the SQL query can be optimized.

3) Number of deadlocks/sec (amount of deadlock/sec): Deadlocks are very harmful to the scalability of the application and can lead to a poor user experience. The value of this counter must be 0.

4) lock Requests/sec (Lock request/sec), the value of this counter can be reduced by optimizing the query to reduce the number of reads.

LoadRunner Monitoring SQL Server