Occurs during generic asynchronous operations. This wait is rare and currently not documented by Microsoft. Values should be minimal. If values are excessively high see the suggested solutions below

Resolved by

DBAs and Developers

Suggested solutions

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

Additional research

Tracking Session and Statement Level Waits

⇐ Back to index