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: Idle
SQL Server versions: 2012, 2014, 2016, 2017

This is an idle wait and so it can be safely ignored.


1 Answer


Waiting to get the lock on the timer task object and is also used for the actual waits between times that work is being performed. For example, for a task that runs every 10 seconds, after one execution, AlwaysOn Availability Groups waits about 10 seconds to reschedule the task, and the wait is included here. Information from Microsoft®

Very rare

This wait never occurs for most instances

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

Prevalence of HADR_TIMER_TASK across the Spotlight Population

For 43 % of hours with this wait, average wait time is around 490 ms

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

164 instances contributed data to this chart

Latency Distribution of HADR_TIMER_TASK across the Spotlight Population