This wait is used internally to acquire the list of locks a transaction holds. It is commonly used during deadlock detection. This wait is uncommon and should be investigated if moderate values are detected

Resolved by


Suggested solutions

  1. Check the SQL Server error log for more information. Look for deadlock events
  2. Examine other wait statistics on the instance. Investigate accordingly
  3. Run an Extended Event session with wait statistics to determine which requests are charging the wait

Additional research

Tracking Session and Statement Level Waits
Detecting and Ending Deadlocks

See more

Consider using ApexSQL Monitor, a Windows and SQL Server monitoring tool able to track SQL Server wait types, including the individual query wait statistics

⇐ Back to index