Brent continues his DBA Training Plan: Whenever your queries need to wait on something – storage, locks, memory, whatever – SQL Server tracks what it’s waiting on, and for how long. It’s like you’re seeing INSIDE the server, with all kinds of possible debug points being tracked. All you have to do is ask SQL Server, “What have you been waiting on?”. Here Brent shows you how.
2019-09-27
This week Steve is wondering if you know how to use waits and queues for troubleshooting.
2019-08-23
646 reads
2019-06-24
794 reads
2019-06-10
1,101 reads
In which you ask your assistant to fetch your coffee, and time them.
2018-10-19
3,120 reads
Paul Randal adds another chapter to his thorough series on knee-jerk wait statistics, focusing on the often-misunderstood PAGELATCH_XX waits.
2015-11-05
5,574 reads
This beginner's guide to Wait Stats by Jonathan Kehayias and Erin Stellato is a free PDF download brought to you by SQL Skills and Simple-Talk.
2014-04-18
5,338 reads
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Hi everyone I asked this earlier but the desired outcome is a bit different...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers