This wait represents SQL Server waiting for non-data page I/O. It is common for this wait to occur during tempdb spill-over from sort and hash operations

Resolved by

DBAs and Developers

Suggested solutions

  1. Check to see if tempdb, data and logs are on separate volumes
  2. Optimize queries experiencing tempdb spillage

Additional research

Causes of IO_COMPLETION and WRITE_COMPLETION SQL Server wait types
Are I/O latencies killing your performance?

⇐ Back to index