Let's hang out in my home office in Vegas and go through your top-voted questions from https://pollgab.com/room/brento. The audio's a little echo-y in this one because I just moved my office down to a small first floor guest bedroom with hardwood floors instead of carpet, and I haven't treated the room for noise yet.
When I first started teaching database sessions at conferences, I noticed a pattern.
When I finished the session, closed PowerPoint, and thanked everyone for attending, a big queue of attendees would instantly start forming at the podium. People would line up to ask private questions, one at a time.
You've been reading my blog, watching my videos, and maybe even taking some of my training classes. You've heard me say things like "my clients" from time to time, and you're wondering... why do companies actually hire me? What problem are they trying to solve?
Well, when clients meet with me for the first time, I have a series of questions I put up on the screen for them to talk through:
Want to ask your own questions or pick the ones I discuss? Head over to https://pollgab.com/room/brento to get involved. In the meantime, let's hang out in the backyard, where Beni makes a special guest appearance.
https://youtu.be/aMMBj4owm3A
Let's hop right into it. I've got one lab server (named Colorful), so when I open the app, my estate overview isn't particularly interesting - yours will be:
Go into the server's details, and you see the top wait types over time:
I know a lot of y'all lag behind on upgrading SSMS, but v22.3 just introduced something that you need to be aware of. It's going to impact any of your users who DO upgrade their SSMS, or who use Github Copilot. There's something that you can do in order to improve Copilot's code quality and make it match your preferred coding standards.
It's an overcast afternoon at Atlantis Paradise Island in the Bahamas, so since I can't go into the water, might as well go through your top-voted questions from https://pollgab.com/room/brento.
https://youtu.be/1c0K-WJ-itk
Two big sets of news this month! The Consultant Toolkit now supports imports to a database so you can track your clients' health and performance over time, and sp_BlitzCache has a new @AI parameter.
Set @AI = 2, and get a prompt you can copy/paste into the AI of your choice to help you tune the query.
Set @AI = 1, and we'll actually call ChatGPT or Google Gemini for you and return the advice.
For SQLBits this year, I wanted to submit a performance tuning session about one of the most classic, timeless problems I run into: why is the same query fast in development but slow in production?
All of my regular readers - if there is such a thing - are now yelling out, "Parameter sniffing!"
On the world's largest floating electronic dance music festival, I took your top-voted database questions from https://pollgab.com/room/brento.
https://www.youtube.com/watch?v=Dk1kb6fM21E
A long time ago in a galaxy far, far away, SQL Server Management Studio was included as part of the SQL Server installer.
Back then, upgrading SSMS was not only a technical problem, but a political one too. Organizations would say things like, "Sorry, we haven't certified that cool new SQL Server 1982 here yet, so you can't have access to the installer." Developers and DBAs were forced to run SSMS from whatever ancient legacy version of SQL Server that their company had certified.
Is your company hiring for a database position as of February 2026? Do you wanna work with the kinds of people who read this blog? Let's make a love connection.
If your company is hiring, leave a comment. The rules:
While in the midst of moving my home office into a new room in the house, I stopped to take your top-voted questions from https://pollgab.com/room/brento. About 18.5 minutes into the recording, my camera overheated because I hadn't set up the fan on it yet, hahaha.
https://www.youtube.com/watch?v=yNAI__FLlxo
Normally, when SQL Server updates statistics on an object, it invalidates the cached plans that rely on that statistic as well. That's why you'll see recompiles happen after stats updates: SQL Server knows the stats have changed, so it's a good time to build new execution plans based on the changes in the data.
However, updates to system-created stats don't necessarily cause plan recompiles.
Sandra Delany (LinkedIn) wrote a well-thought-out blog post called, "Should a SQL Server DBA Know Windows Clustering?" She's got about 20 years of DBA experience, and she works for Straight Path (a firm I respect) as a consultant. You can probably guess based on her background that yes, she believes you should know how to set up, configure, and troubleshoot Windows clustering. It's a good post, and you should read it.
When I travel, I try to take y'all with me to really pretty or at least interesting locations. On my Tokyo visit last year, I did Office Hours in Akihabara, the electronics & anime shopping hub. Even though I'm not into anime at all and I don't collect that kind of gear, I wanted to see it because it's famous among geeks.
SQL Server 2025 Cumulative Update 1 came out last week, and I was kinda confused by the release notes. They described a couple dozen fixed issues, and the list seemed really short for a CU1. However, the more I dug into it, the weirder things got. For example, there were several new DMVs added -…
A private equity (PE) company recently acquired the majority of Redgate Software, the current owners of the PASS Data Community Summit and SQLServerCentral. Everybody in tech has private equity stories, some good, some terribad. Private equity hands money to companies not out of generosity, but because they believe they can turn it into even more money…
Kyoto feels like a timeless, classic version of historical Japan with quiet tree-lined streets, giant temples, and bubbling brooks. It's the exact opposite of last week's experience in noisy Osaka! Last year, I filmed in Kyoto outside a temple, and this year, I'm at another temple just after New Year's, the time when Japanese folks traditionally go to visit their many gorgeous temples.
It's time for our quarterly update of our SQL ConstantCare® population report, showing how quickly (or slowly) folks adopt new versions of SQL Server. In short, people are replacing SQL Server 2016 and 2017 with 2022!
SQL Server 2025: 0% (but it's 10 servers)
SQL Server 2022: 29%, up from 25% last quarter
SQL Server 2019: 43%, no change
SQL Server 2017: 9%, was 10%
SQL Server 2016: 10%, was 13%
SQL Server 2014 & prior: 6%, no change
Azure SQL DB and Managed Instances: 2%, no change
