This wait type accumulates while the Log Manager is waiting for space to become available (via log truncation) to write transaction records to disk. If this wait type is high it indicates the transaction log is frequently running out of space

Resolved by

DBAs and Developers

Suggested solutions

  1. Preallocate transaction log files
  2. Increase the auto-growth from the default (less frequent growths)
  3. Remove cursor or iterative procedures making many small changes. Replace these with batch modifications
  4. Upgrade the volume the transaction log(s) are stored on
  5. Ensure that index fill factors are set appropriately to avoid page splits. Indexes that are frequently changing should have a lower fill factor. Page splits require additional transaction log records

Additional research

Sizing Your Transaction Log

See more

Consider using ApexSQL Monitor, a Windows and SQL Server monitoring tool able to track SQL Server wait types, including the individual query wait statistics

⇐ Back to index