Waitopedia is a comprehensive resource of information about SQL Server waits.

The description shown below is the top answer as voted by the Spotlight community.

The charts are based on 2.1 TB of data collected from 4207 instances uploaded by 323 Spotlight users over an 8 week period.


Category: Other
SQL Server versions: 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017


1 Answer


Occurs when SQL Server polls the version transaction manager to see whether the timestamp of the earliest active transaction is later than the timestamp of when the state started changing. If this is this case, all the snapshot transactions that were started before the ALTER DATABASE statement was run have finished. This wait state is used when SQL Server disables versioning by using the ALTER DATABASE statement. Information from Microsoft®

Very rare

This wait never occurs for most instances

For each of 4207 instances, we ranked DISABLE_VERSIONING on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of DISABLE_VERSIONING across the Spotlight Population

For 67 % of hours with this wait, average wait time is around 2 seconds

For each instance, we found all the recent hours when it had a DISABLE_VERSIONING wait. We found the average latency for each of those hours.

1 instance contributed data to this chart

Latency Distribution of DISABLE_VERSIONING across the Spotlight Population