MS SQLServer: Locks: Lock Waits / Sec: _Total - HOW TO REMEDY?
Lock waits/second is creeping upward - 15 to 20 is not uncommon. Is this something which should concerning? What can be done to lower lock waits/sec? Thank you!
7. SQLServer: Locks: Lock Waits / Sec: _Total
In order for SQL Server to manage concurrent users on the system, SQL Server needs to lock resources from time to time. The lock waits per second counter tracks the number of times per second that SQL Server is not able to retain a lock right away for a resource. Ideally you don't want any request to wait for a lock. Therefore you want to keep this counter at zero, or close to zero at all times.
Screencap-1962-Aug.-18-15.13.jpg
7. SQLServer: Locks: Lock Waits / Sec: _Total
In order for SQL Server to manage concurrent users on the system, SQL Server needs to lock resources from time to time. The lock waits per second counter tracks the number of times per second that SQL Server is not able to retain a lock right away for a resource. Ideally you don't want any request to wait for a lock. Therefore you want to keep this counter at zero, or close to zero at all times.
Screencap-1962-Aug.-18-15.13.jpg
ASKER
How do you go about capturing and analyzing the longer queries? I have no users complaining about query length. It's my monitoring Solar Winds that is noticing the steady rise in lock wait/sec and I'm trying to head off the issue before it becomes noticeable to users or starts causing some other problem. Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great - thanks Vitor!
Capture and analyze the queries that are taking longer to run. 15 to 20 seconds is already a slow query. For me, everything that is take more than a second is considered slow unless is a report.