Occurs while SQL Server is waiting for the Operating System to complete portions of write operations. This wait is commonly seen in databases with auto-growth not configured appropriately. Small values are expected. Excessive values should be investigated

Resolved by

DBAs and Developers

Suggested solutions

  1. Enable Perform Volume Maintenance Tasks to avoid zero-initialisation for data files
  2. Increase the auto-growth from the default (less frequent growths)
  3. Investigate storage issues in the Windows Event Viewer
  4. Upgrade storage
  5. Consolidate transactions from row-by-row statements to batch processing

Additional research

PREEMPTIVE_OS_WRITEFILEGATHER and Instant File Initialization (IFI)
Some Initial Insert Test Benchmarks on SQL Server 2008 R2

⇐ Back to index