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: Lock
SQL Server versions: 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017


1 Answer


Large waiting time on this resource indicates that the server is executing queries on top of sys.dm_os_waiting_tasks, and these queries are blocking deadlock monitor from running deadlock search. This wait type is used by deadlock monitor only. Queries on top of sys.dm_os_waiting_tasks use DEADLOCK_ENUM_MUTEX. Information from Microsoft®

Very rare

This wait never occurs for most instances

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

Prevalence of DEADLOCK_TASK_SEARCH across the Spotlight Population

For 86 % of hours with this wait, average wait time is less than 1.6 ms

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

322 instances contributed data to this chart

Latency Distribution of DEADLOCK_TASK_SEARCH across the Spotlight Population