Is It a Problem?
No. Microsoft says it is expected between deadlock detections, and lengthy total waiting time on this resource doesn’t indicate a problem. Get Wait Statistics filters it out by default.
What It Means
It is the deadlock monitor waiting to start its next search. The interval is usually five seconds and contracts and expands with how often deadlocks occur. Our SQL Server 2025 lab matches: about 14,800 waits averaging 5.0 seconds.
When It Does Matter
It does not. In principle, more and shorter waits mean the monitor has been finding deadlocks, but there is a direct record: the system_health Extended Events session keeps every deadlock graph. Get Deadlock Summary reads them, and Reading and Fixing a SQL Server Deadlock walks through one. The baseline to monitor is the number of deadlocks per day, not this wait.
Where To Go Next
REQUEST_FOR_DEADLOCK_SEARCH is background noise on a healthy instance. If you are chasing a real problem, start with the waits that cost you time.
- Get Deadlock Summary, the deadlocks system_health has recorded.
- The waits that usually matter, ranked, with what each one is telling you.
- Performance & Troubleshooting, the scripts and guides for this part of the stack.
Leave a Reply