Similar to IO_COMPLETION, except this counter is present more for instances using database snapshots and performing some transaction log operations

Resolved by

DBAs and Developers

Suggested solutions

  1. Decrease number of database snapshots (if applicable)
  2. Clean up transaction log internal fragmentation (decrease number of VLFs to a suitable amount)

Additional research

Causes of IO_COMPLETION and WRITE_COMPLETION SQL Server wait types
High Virtual Log File (VLF) Count

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