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
659 reads
2019-06-24
795 reads
2019-06-10
1,103 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 Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers