Description
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
- Safe to ignore if LOGBUFFER and WRITELOG are low
- 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
See more
Check out SpotLight, a free, cloud based SQL Server monitoring tool to easily detect, monitor, and solve SQL Server performance problems on any device