This wait occurs on databases with snapshots. When the primary database is updated the original page must be written to any snapshots. The wait will also accumulate during DBCC CHECKDB operations as a snapshot is temporarily created internally

Resolved by


Suggested solutions

  1. Drop any unnecessary snapshots
  2. Upgrade disks hosting snapshot data files

Additional research

Database Snapshots
Looking at Database Snapshot Performance

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