How to See Rowcounts and Execution Time for In-Flight Queries in SQL Server
I frequently need to see rowcounts and execution time for queries while they’re running. Maybe I’m troubleshooting a slow query …
Read MoreBy Kendra Little on • 2 min read
When I first created SQLWorkbooks, I distilled what it was all about down into one sentence: “Learn SQL Server by Solving Problems.”
This month, I introduce my first SQLChallenge, which distills that down into practice. The SQLChallenge features 23 minutes of video with scripts that you can use to reproduce and solve the problem yourself.

In this SQLChallenge , you get:
Your challenge: Design an index that prevents the deadlock from happening when the repro steps are run again
After you’re done working on preventing the deadlock, watch the videos showing how I strategized the solutions, and indexes I tested that prevent the deadlock (you get these, too, in the solution script).
In the videos where we defuse the deadlock together, you will learn:
Getting stuck is totally OK – it’s the struggle that gets you there in the end!
If you get totally frustrated, go ahead and watch the solution videos.
Then set yourself a reminder to retake the challenge in one week’s time. Running through the challenge again will lock in the learning.
I wouldn’t leave you without a safety net.
The SQLChallenge links you to a course which explains more of the background on what deadlocks are, how to capture deadlock graphs, and even more info on how to solve deadlocks – with a totally different deadlock example.
Even if you’ve never faced off with a deadlock before, you can solve ’em!
Check them all out here.
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.