This wait type accumulates during flush operations by the SQL Server Log Manager. Microsoft has not documented this wait type so little is known about it. However, the wait is common and small values do not appear to cause issues

Resolved by

DBAs and Developers

Suggested solutions

  1. Examine other wait statistics, in particular LOGBUFFER and WRITELOG
  2. Remove cursor or iterative procedures making many small changes. Replace these with batch modifications
  3. Upgrade the volume the transaction log(s) are stored on

Additional research

Diagnosing Transaction Log Performance Issues and Limits of the Log Manager
What is the WRITELOG wait type

⇐ Back to index