Indicates SQL Server is waiting for transaction log disk writes to complete. If the value is high it could indicate a disk bottleneck on the volume hosting the transaction logs

Resolved by

DBAs and Developers

Suggested solutions

  1. Upgrade storage volume hosting the transaction logs
  2. Disable any unused indexes. This will decrease the number writes during data modifications
  3. Ensure that index fill factors are set appropriately to avoid page splits. Indexes that are frequently changing should have a lower fill factor
  4. Remove cursor or iterative procedures making many small changes. Replace these with batch modifications

Additional research

How to handle the SQL Server WRITELOG wait type
Diagnosing Transaction Log Performance Issues and Limits of the Log Manager
What is the WRITELOG wait type

⇐ Back to index