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: 2012, 2014, 2016, 2017


1 Answer


Occurs on the versioning state change of an AlwaysOn secondary database. This wait is for internal data structures and is usually is very short with no direct effect on data access. Information from Microsoft®


This wait has never occurred recently

HADR_DATABASE_VERSIONING_STATE has not occurred recently on 4207 instances checked.

Prevalence of HADR_DATABASE_VERSIONING_STATE across the Spotlight Population