I am SQL Server Performance Tuning Expert at @SQLAuthority
Joined May 2007
- Tweets81.7K
- Following437
- Followers30.9K
- Likes0
Pinned Tweet
SQL Server is changing.
AI is changing how we work with databases.
I spend my time exploring where the two meet.
Here you will find:
SQL Server performance tuning
Query tuning and troubleshooting
Practical AI ideas for DBAs
Real-world scripts and demos
Lessons from actual performance problems
No hype. No fluff.
Just practical learning around SQL Server, performance, and AI.
Follow if that is your kind of content.
SQL Server Developer Edition: Free Download Links From SQL Server 2017 to SQL Server 2025
Two questions come up again and again. Which download should I pick for a demo, a class or a new project? And a week later: can we keep using it for the real app? Start with the download table below, then read the production limits before you build anything on it.
blog.sqlauthority.com/2026/1…
AI Basics: The Four Circles, and Four More Questions
Part one of ten. Most AI interview questions start here, even for senior roles. Someone asks you to explain a large language model in plain words, and your answer tells them more than your resume does.
1. What is the difference between AI, machine learning, deep learning and generative AI?Think of four circles, one inside the next. AI is the widest: any system that does work we’d call judgment. Machine learning sits inside it and learns patterns from data instead of hand-written rules. Deep learning uses many-layered neural networks, and everyday generative AI uses them to create something new. DataWarehousing GuideWhy it matters. All four can show up in one data platform. A fraud score trained on last year’s transactions is machine learning. The assistant that drafts your query is generative AI.
blog.sqlauthority.com/2026/1…
The fog after a layoff shows up before the grief does, and nobody warns you about it. The mind that carried a whole career can’t hold a grocery list. It’s frightening. It’s also normal, and it lifts.
I’ve written about the last day in A Letter for the Night Your Job Ends. The money got its own post, Jobs Are Disappearing Quietly. This one is about the weeks in between, when your own mind feels like a road you can’t see.
One note first: I’m not a doctor or a therapist, and this isn’t medical advice. For twenty-five years, companies have called me on their worst day. I’ve watched a lot of people walk through the weeks after a job ends. This is what I’ve seen help.
Read more here: blog.sqlauthority.com/2026/0…
It would nice to have a wake code for DOT like Hey Google or Alexa or something. Currently we have to make a call to start the conversation. @OpenAI or it may be there and I missed.
The Puzzle, With Pins and String
Picture a corkboard, a box of pins and a spool of red string. Cut every piece of string to exactly the same length. Now push in some pins, and stretch a string between every pair that sits exactly that far apart.
The question sounds simple. With a hundred pins, or a million, what is the largest number of strings you can fit? You can place the pins anywhere you like. Every string has to be exactly one unit long, though, not almost.
Small cases are fun to play with. Three pins in an equilateral triangle give three strings. Four pins in a diamond of two such triangles give five. Seven pins, a regular hexagon around a center pin, give twelve.
Read: blog.sqlauthority.com/2026/0…
Your SQL query did not change.
Your indexes did not change.
Your server did not change.
So why did the query suddenly become slow?
One possibility that is surprisingly easy to overlook:
SQL Server statistics are describing yesterday’s data.
The Query Optimizer makes decisions based on statistics. It uses them to estimate how many rows will be returned, then chooses joins, memory grants, access methods, parallelism, and ultimately the execution plan.
If those statistics no longer represent the current data, SQL Server can make a perfectly reasonable decision based on completely outdated information.
I recently tested this on SQL Server 2025.
I created a table with 1 million rows spread across 400 days, then added 20,000 new rows for today without crossing the statistics refresh threshold.
The query returned 20,000 rows.
But the estimate?
Current Cardinality Estimator: 6,000 rows
Legacy Cardinality Estimator: 1 row
Yes. One.
In another test, stale statistics with legacy estimation resulted in 120,043 logical reads.
After updating the relevant statistic, the estimate became 19,867 rows and the resulting plan used 18,220 logical reads.
The important lesson is not simply:
"Update statistics and everything becomes faster."
It is this:
When SQL Server performance changes without an obvious reason, compare estimated rows with actual rows.
Sometimes the optimizer is not making a bad decision.
It is making the best decision it can using an outdated description of your data.
I explain the experiment, auto-update thresholds, sampling, the ascending key problem, FULLSCAN, PERSIST_SAMPLE_PERCENT, and what you should actually check in production here:
blog.sqlauthority.com/2026/0…
Have you ever fixed a mysterious SQL Server performance problem simply by updating statistics?
#SQLServer #DatabasePerformance #PerformanceTuning #SQL #Database #DBA #QueryOptimization #MicrosoftSQLServer
May be we all got this wrong - They may be reducing the API costs so much that current $200 plan will have better usage than what we are getting today.
Hi,
Tomorrow we are re-opening the Pro $200 subscriptions to new subscribers, but together with it we are also changing how we calculate the usage for it. In effect, if you do the math, it will net out at half the dollar in API spend compared to the old Pro $200 plan.
Now that it's said, let me explain why this is happening and why you will still get more work done than if you were on the Pro $200 subscription one month ago.
(a) We didn't want to compromise in other ways and are committing to not reintroducing the 5h limit, so that you can fully use the weekly usage when you want.
(b) On the subscription, we guarantee that over time you always get more work done and with an increasing level of quality. This means that you will continue to get more value per dollar spent as a result of models getting more efficient and us passing down the improvements in the form of API price reductions.
(c) We don't want to put an incentive on ourselves to artificially inflate the API list prices to make it look like you are getting a lot (and workaround it through discounts, etc). Instead we want to continue to both rapidly reduce prices and increase capabilities of models on the API. This week we introduced GPT-6 Sol and GPT-6 Luna at 50% of their previous price. Over time, we see prices go low enough that it makes sense for most to buy usage as needed without there being a significant gap between what you get in a subscription and what you get in the API for a dollar spent.
(d) Tomorrow, we are adding more things to the subscription that won't draw on the usage, I won't reveal what that is yet.
I wanted to be transparent before all the big announcements tomorrow. Lots of new exciting things are coming to the subscriptions that will make it super compelling, but I wanted to make sure to share this change ahead of time so you can all understand it before we shower you with good news.
Codexingly,
Tibo
AI Generated ETL Worked on Day One. Then Came Monday.
The job itself was nothing special. A vendor drops a CSV file on a share every morning. We check it, fix up a few columns, and merge about three hundred thousand rows into a warehouse table. If you work with data, you’ve built this job more than once.
I described the source, the target and the rules, and asked AI to write it. What came back was good. It had a staging table, a proper merge, logging, and sensible error handling around the file read. It ran on the first try, the numbers matched, and everybody was happy. I’ll admit I was a little disappointed. I had a whole “I told you so” ready.
The job it replaced was written in 2016 by someone who had left the company years ago. It wasn’t pretty. It had odd IF checks, a hash lookup, and a wait loop nobody could explain. On day one, the new code was better, and I’d have said so to anyone who asked.
blog.sqlauthority.com/2026/0… read More
Two query lines are on the page. One looks longer. Look once, make a choice, and then look again.
I have spent years looking at execution plans. The lines, boxes and arrows can make an expensive operation look important before I have read a single number. That is useful when the picture points me to a place worth investigating. It is less useful when I start treating the size of a drawing as evidence.
For today's Sunday puzzle, look at the two dark horizontal lines in the picture. The upper one sits near the narrow end of a server aisle. The lower one sits near the wide end. Do not measure them yet. Which line looks longer to you? If someone else is nearby, ask them before you scroll. It is more fun when two people are confidently wrong in different directions.
The illustration was drawn to a fixed grid. There is no animation and nothing changes when you look away. Give your eyes five seconds, then read the answer.
blog.sqlauthority.com/2026/0…
My 18th & 19th books are here!
I never expected “100 AI Interview Questions” to receive so much love. It’s on track to outsell “AI: Nobody’s in There.”
Seems this was what people needed. Thank you ❤️
blog.sqlauthority.com/2026/0…
blog.sqlauthority.com/2026/0…
The author copies of my 18th and 19th books have arrived.
Nineteen books, and this part still makes me pause. Seeing your words on a screen is one thing. Holding the printed pages is another.
These two books explore questions I care about.
📖 AI: Nobody’s in There. But we’re still in here.
Thirty short essays about AI, work, learning, and the human judgment we still need. For anyone trying to understand how this change feels, alongside what it does.
The story behind the book:
blog.sqlauthority.com/2026/0…
📖 100 AI Interview Questions and Answers for Data Professionals
A practical book with 100 questions, 184 key terms, and short answers you can practice aloud. For data professionals who want to explain what they know clearly when the conversation turns to AI.
The announcement includes questions you can try:
blog.sqlauthority.com/2026/0…
Today, I wanted to share the photograph and say thank you. If you have read my work, asked a thoughtful question, or pointed out something I missed, you have helped make the writing better.
Which one would you open first?
I honestly don’t know how to react.
So many of you have bought my AI Interview Questions book, and quite a few have even asked me to send them the PDF so they can share it freely with friends.
Part of me smiles at that. Part of me doesn’t know what to say. 😊
But I do want to say this:
This is not just another AI book I put together quickly.
I spent a lot of time, thought, research, rewriting, and effort on it. I genuinely tried to create something useful, practical, and worth your time.
So seeing people interested in it, buying it, talking about it, and wanting to share it means more to me than I can properly express.
Thank you for all the love. ❤️
blog.sqlauthority.com/2026/0…
[Just released my 19th book]
100 AI Interview Questions and Answers for Data Professionals: From Keywords to Concepts
AI has walked into every data interview. A vague answer can cost you the offer.
This book gives you the 100 AI questions data interviewers ask, with plain answers you can say out loud in about thirty seconds. Each answer shows why it matters at work, what the interviewer is listening for and the trap that catches people.
It's written for every data professional: DBAs, data engineers, analysts, developers and architects, on any database and with any AI tool.
I have spent a lot of time building this book and I am very much looking forward to your opinions.
The books is available in three format: Print, Kindle eBook and Audio Book.
Link in the first comment. I am very much interested in your feedback about this book.
