The number of SQL batch requests per second has fallen below the threshold level.
Impact : Medium
This metric represents the number of SQL requests that are being executed per second and is an indication server performance.
Expected behavior :
There is no standard metric for number of requests . You should set your own thresholds after reviewing past behavior.
Using AimBetter monitor, identify any queries that have remained open for an inordinate length of time. Recover the query plan, and see whether any improvements are available.
Missing or corrupted indexes can lead to queries working inefficiently and consuming resources.
See our recommendations regarding memory optimization here.
SQL Server Batch Requests metric represents the number of SQL requests that are being executed per second. This metric is a strong representation of how the server is performing, but should not be viewed in isolation. It is necessary to correlate with other Observer resources, especially CPU usage, disk and network traffic, memory levels etc. in order to get an overall understanding of server’s load. The target for good SQL Server behavior is to achieve the highest number of requests per second while consuming the lowest level of resources.
Peak throughput is heavily dependent on the architecture of the system, coding standard of queries and procedures, tables and index design. A low reading of batch requests will be an indicator of a bottleneck in one or more areas.
AimBetter provides a comprehensive overview of all the relevant metrics that make Batch Request levels such a powerful gauge, compared to the raw information that PerfMon will return, which is restricted to the single picture of request behavior without reference to all the other contributing factors to overall performance.