This wait type accumulates while the SQL Server Log Manager is waiting to receive requests. As this is an idling wait high values do not indicate a bottleneck. However, if the LOGBUFFER or WRITELOG values are high then investigation is required

Resolved by

DBAs and Developers

Suggested solutions

  1. Safe to ignore if LOGBUFFER and WRITELOG are low
  2. Remove cursor or iterative procedures making many small changes. Replace these with batch modifications
  3. See if the database setting Delayed Durability is suitable for the database system
  4. Disable any unused indexes. This will decrease the number writes during data modifications
  5. Ensure that index fill factors are set appropriately to avoid page splits. Indexes that are frequently changing should have a lower fill factor

Additional research

Delayed Durability in SQL Server 2014
Diagnosing Transaction Log Performance Issues and Limits of the Log Manager
What is the WRITELOG wait type

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