For T-SQL Tuesday #100, Adam Machanic's challenge for SQL bloggers was to predict what databases would be like 100 months from then.
Well, guess what: that's coming up this July!
Is your company hiring for a database position as of June 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:
In this live stream recording, I'll show you how to use the latest features of sp_BlitzCache to rapidly improve performance on an existing server. I'll show you how to find your server's top bottleneck, find the queries causing that bottleneck, and then demonstrate how to get advice from AI on how to tune them in seconds.
You might notice that the advice you get from Copilot in SSMS isn't very good, but it isn't necessarily AI in general. Part of the problem is something specific about SSMS Copilot and the way it prompts LLMs, and I wish I could tell you exactly what it is, but I can't because I don't have access to how SSMS is changing your prompts.
You were minding your own business, and all of a sudden it happened.
You glanced at file sizes one day, and your eyes got big. The numbers got a little large while you weren't looking. This is a great time to stop and think about a few changes to the way you're managing this database.
In this 76-minute session, I'll show you how to use the latest features of sp_BlitzIndex to rapidly improve performance on an existing database. I'll show you how to figure out quickly if you've got too many indexes or not enough, and then demonstrate how to get advice from AI on how to consolidate them in seconds.
Can I be honest with you for a second?
It makes my skin crawl when I hear database people smugly answer a question with "It depends!"
If you do a lot of query tuning, you've probably come across Richie Rump's StatisticsParser.com. Now, it's even easier to use.
Now, it's even easier to use. Download & install it, then run your query with SET STATISTICS IO, TIME ON, and after it finishes, right-click in the query window and click Parse Statistics:
Our cruise ship pulled into port in Victoria, Canada, so before we head out to the Butchart Gardens, let's go through your top-voted questions from https://pollgab.com/room/brento.
https://www.youtube.com/watch?v=MDTuQFiXo2s
I love me some documentation.
For years, I've pointed folks to the SQL Server 2008 documentation on Forced Parameterization, a really useful tool for reducing plan cache bloat, getting more accurate reusable query plans, and enabling SQL Server 2019 and 2022's Intelligent Query Plan features, many of which rely on the same query text coming in repeatedly over time in order to tune it. That documentation was pretty sparse, though.
At least once a month, I get this question from a client:
We have big data, and we want to save money. We want to move the older data down to some kind of archives that will cost us less.
Is your company hiring for a database position as of May 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:
I get a lot of emails like this:
Hi! I built an app. Can you take a look at it, give me your feedback, and then help get the word out to your readers?
When there are IF branches or conditional logic, "Edit Query Text" only shows you the branches that actually executed. It's easy to miss whole swaths of code that didn't happen to execute one particular time.
To demo it, let's create a simple stored procedure with an IF branch that sometimes executes, and sometimes doesn't:
In theory, SQL Server performance monitoring is pretty simple:
Review the server's top wait types
Find the queries causing those wait types
Fix those queries, or improve the way the server reacts to them (indexes, settings, etc.)
I asked y'all to make the comments on this post look like my ChatGPT history, and y'all understood the assignment. The answers were all over the place from accurate to humorous. Here are the 5 runners-up first, each of whom won a Fundamentals Bundle for themselves or someone they love, since many of these folks already had a Fundamentals membership:
I flew into Wales a couple days early to get used to the time zones, and showed up at the conference center where SQLBits would be located. Let's go through your top-voted questions from https://pollgab.com/room/brento on a very chilly morning:
https://www.youtube.com/watch?v=6XjBwH7NzfA
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. There were only slight 1-2% shifts, nothing big:
SQL Server 2025: 1%
SQL Server 2022: 31%, up 2% from last quarter
SQL Server 2019: 42%, down 1%
SQL Server 2017: 9%, no change
SQL Server 2016: 9%, down 1%
SQL Server 2014 & prior: 6%, no change
Azure SQL DB and Managed Instances: 2%, no change
When you turn on last actual plans in SQL Server 2019 and newer:
[crayon-6af15a895ae6f399318047/]
This week at the SQLBits conference in Newport, I'm teaching an all-new all-day session called Dev-Prod Demon Hunters: Finding the Real Cause of Production Slowness.
It filled up initially, but they've opened up more seats for it, so if you're interested, there's still time to join! Attendees get a free Fundamentals & Mastering 1-Year Bundle. Register now for SQLBits, or if you're already registered, email contactus@sqlbits.com to get into my workshop.
