Description
Indicates SQL Server is waiting for a log buffer to write log blocks for a transaction. Log buffers often deplete when a lot of small transactions (implicit or explicit) are happening very frequently
Resolved by
DBAs and Developers
Suggested solutions
- Remove cursor or iterative procedures making many small changes. Replace these with batch modifications
- See if the database setting Delayed Durability is suitable for the database system
- Disable any unused indexes. This will decrease the number writes during data modifications
- 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