A background task that processes Windows Server Failover Clustering notifications is waiting for the next notification. Internal use only. 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_NOTIFICATION_DEQUEUE
Category: Idle
SQL Server versions: 2012, 2014, 2016, 2017
This is an idle wait and so it can be safely ignored.
What is HADR_NOTIFICATION_DEQUEUE?
1 Answer
|
|
answered 3318 days ago
Spotlight Essentials
|
|
|
This wait never occurs for most instances
For each of 4207 instances, we ranked HADR_NOTIFICATION_DEQUEUE on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.
Prevalence of HADR_NOTIFICATION_DEQUEUE across the Spotlight Population
For 33 % of hours with this wait, average wait time is around 18 minutes
For each instance, we found all the recent hours when it had a HADR_NOTIFICATION_DEQUEUE wait. We found the average latency for each of those hours.
139 instances contributed data to this chart