A query on object(s) in a readable secondary database of an AlwaysOn availability group is blocked on row versioning while waiting for commit or rollback of all transactions that were in-flight when the secondary replica was enabled for read workloads. This wait type guarantees that row versions are available before execution of a query under snapshot isolation. Information from Microsoft®
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.
HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING
Category: Other
SQL Server versions: 2012, 2014, 2016, 2017
What is HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING?
1 Answer
|
|
answered 3318 days ago
Spotlight Essentials
|
|
|
This wait never occurs for most instances
For each of 4207 instances, we ranked HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.
Prevalence of HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING across the Spotlight Population
For 83 % of hours with this wait, average wait time is around 4.9 seconds
For each instance, we found all the recent hours when it had a HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING wait. We found the average latency for each of those hours.
1 instance contributed data to this chart