The SQL Server Response Time (Millisecond) alert provides the time (in milliseconds) SQL Diagnostic Manager currently needs to send a simple SQL command to the SQL Server instance, have it processed, and receive the returned result set.

High response times generally occur when sessions are blocked or when either there is heavy network traffic or network problems or when either the computer the SQL Diagnostic Manager Repository or the computer the SQL Diagnostic Manager Console is hosted on is running slow due to various problems.

Typically, this value should average below 2000 ms for a well tuned network and server. Average values in excess of 2000 ms indicate either an excessively busy network segment or a stressed SQL Server.

Reduce your SQL Server response time

A common cause to high response times is when sessions are being blocked. To fix this problem, go to the Sessions tab and select the Blocking view to see if any sessions are blocking. You can then select the session and click either Trace Session to see what queries the session is creating and to see what is causing the block, or Kill Session to stop it.

To enable alerting when this metric is outside its established baseline, click the Baseline Thresholds Enabled (as percentage of baseline) check box in the Alert Configuration window.



IDERA ProductsPurchase | Support | Community | Resources | About Us | Legal