SQL Server limits, done the way a record book does them. Not what the documentation says, but what happened when I tried one more. Eleven records, each attempted on SQL Server 2025 build 17.0.4085.5, each with the exact error text at the edge. One documented figure turned out to be wrong on this…
SQL Server emergency? Email pinal@sqlauthority.com with URGENT in the subject line.
SQL Server Triggers on Trial: The State Versus the Trigger
SQL Server triggers, tried in open court. The prosecution says they’re slow, hidden and wrong. The defence says they’re the only witness in the room. Four exhibits were measured on SQL Server 2025, and the judge rules at the end.
SQL Server Blocking at 2 a.m.: You Are the On-Call DBA
SQL Server blocking, told as a choose-your-own-path story. You are the on-call DBA. The phone has gone. The diagnosis and the kill were run in the lab on SQL Server 2025 and measured. The other branches are reasoned, and the text says which is which.
20 Years of SQLAuthority: Twenty Books, One Family, and a Diary That Grew Up
20 years of SQLAuthority started with one query saved on November 1, 2006. Almost 6,000 posts later, there are nineteen books of mine and one by Shaivi on our shelf. This is the story, and a thank you to Nupur, to Shaivi and to you.
AI Read the Procedure Nobody Dares to Touch
AI read the procedure that everybody walks past. Nine hundred lines, no comments, one very old warning at the top.
Find the Query That Ran at 3 a.m.: A Wanted Poster
How to find the query that ran at 3 a.m. after the fact. It uses nothing but what SQL Server 2025 keeps on its own. I planted a culprit, gave it eight disguises and buried it in four hundred innocent lookups. Then I tracked it down with Query Store. This is the poster.
Claude on SQL Server: Read, Prove, Then Change
Claude on SQL Server is safe when production gives it eyes and nothing else. This post splits the loop into three stages: start this week with a read-only login, make it a daily habit with a past cases library, then run it on a schedule with a second opinion. I tested the login on SQL Server 2025.
SQL Server slow? Let's fix it together in about four hours.
In my Comprehensive Database Performance Health Check, you share your screen, I guide you, and we fix your biggest performance troublemakers. No passwords. No remote access.
You keep every script, and the know-how to fix it yourself next time.
Want your whole team to learn it?
My Practical Workshop has no PowerPoint, just live demos. My AI Enablement Workshop shows your team where AI saves hours, and where it quietly costs them.
Over 400 customers have worked with me this way, and not one shared a password. See all consulting options.