This uncommon wait type occurs during database shutdown when SQL Server is waiting on outstanding disk I/O to complete on the transaction log. Database shutdown occurs when the SQL Server service is stopped. Small values are acceptable. If values are large further investigation is required

Resolved by

DBAs and Developers

Suggested solutions

  1. If possible only stop the SQL Server service in non-peak times
  2. Upgrade the volume the transaction log(s) are stored on
  3. Remove cursor or iterative procedures making many small changes. Replace these with batch modifications
  4. Disable any unused indexes. This will decrease the number writes during data modifications

Additional research

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

⇐ Back to index