This wait occurs when a request is waiting to acquire a shared lock. This typically happens when read requests are blocked by write transactions (implicit or explicit) that have been kept open for extended periods of time

Resolved by

DBAs and Developers

Suggested solutions

  1. Keep transaction durations short.
  2. Ensure transactions isolation levels are appropriate (avoid SERIALIZEABLE and REPEATABLE READ if possible).
  3. Investigate enabling the READ_COMMITTED_SNAPSHOT database setting.
  4. Run trace/Profiler/Extended Event session in conjunction with Blocked Process Threshold to determine which queries are being blocked.
  5. Indexing, ensure that long running queries and transactions are optimized.
  6. Ensure that row, page and table locks are being escalated correctly. If the table is partitioned consider enabling partition escalation.

Additional research

Reducing SQL Server Locks
Understanding Isolation Levels
Identify the Cause of SQL Server Blocking
Lock Escalations

⇐ Back to index