SQL Server cost optimization has a problem nobody puts on the slide. The savings are real, the dollars are real, and none of it reaches the invoice. This is the story of how I found that out in front of people.
I want to tell you about the best week of work I did last year, and then about the two hours at the end of it that I am significantly less proud of.
There was a query on the busiest instance in the estate doing four point one million logical reads. I spent three days on it. Statistics, an index, a rewrite, all the parts nobody photographs. When I finished it was doing nine thousand. CPU on that server dropped sixty eight percent.
That is a genuinely good week. You do not get many of those.
Then I spent two more hours building a report about it, because that is what you do now, and I put a large dollar figure at the top. Forty thousand a year.
I chose a font for that report. I would like that on the record. I sat there, a grown adult with a mortgage, auditioning fonts.
Three days on the fix. Two hours on the report. Guess which one I showed people.
A quick note. Details here are blended across engagements and changed so that nothing identifies a client.
Which Invoice Did It Come Off?
Somebody in finance asked me one question about that report and I have thought about it most weeks since.
There was no edge in it. They were not trying to catch me out. They were holding a document with a big number on it and they wanted to know something entirely reasonable, in the way that finance people do, calmly, while you slowly realise your afternoon has changed.
They asked which invoice it came off.
I did not have an answer. It came off none of them.
The servers were bought in 2022. The licences were paid in March and would have been paid whether I had spent that week tuning a query or learning the guitar. The rack draws roughly the same power at nine thousand reads as it did at four million. Nothing I had done changed a single figure anybody in that building was ever going to pay.
It was not a hard question. It was the easiest question in the world. It just happened to be the one question I had not thought to ask myself, which is usually how these things go.
What I Was Actually Embarrassed About
Here is the part that took me a year to admit, and it is the only reason this post exists.
I was not embarrassed about the arithmetic. Arithmetic is fine. You learn something, you feel briefly stupid, you move on and you are better afterwards.
I was embarrassed because the question had accidentally shown me what I had been doing.
I had spent three days fixing something and two hours making it legible.
And I was prouder of the two hours.
Twenty Years of Nobody Looking Up
Let me be fair to all of us, though, because there is a reason we reached for money and it is not vanity.
For twenty years we counted in the only language we had. Logical reads. Wait statistics. Page life expectancy, which is the most beautiful phrase our profession has ever produced and has never once moved a budget by a single rupee.
I have said the words buffer cache hit ratio out loud in a room containing a chief financial officer. I watched that phrase land the way a stone lands in a very deep well. Eventually. Somewhere. Quietly. Not on anybody.
You can hold an entire company upright for eleven years and still be referred to in the leadership meeting as the one who does the database thing.
And then somebody worked out that a query could be expressed in money, and for the first time in two decades, people turned around.
Of course we grabbed it. I would grab it again. I grabbed it so hard I picked a font.
The Feeling I Mistook for Competence
But I want to name what that report actually gave me, because I had it wrong at the time and I doubt I am the only one.
It did not make me feel competent. I already knew the fix was good. I did not need a bar chart to confirm that, and the bar chart did not know anything about indexes.
It made me feel visible.
Those are two completely different feelings and I could not tell them apart. If you have spent a long time doing invisible work, you know exactly which one you are hungry for, you know how badly, and you know it never turns up wearing a name badge that says I am hunger. It turns up dressed as professionalism.
What a Borrowed Currency Quietly Does to You
This is where it stops being a story about a report and starts being a story about the next two years.
When you agree to be measured in a currency, you do not just get measured in it.
You start choosing in it.
It happens slowly and it feels like maturity the entire time it is happening. You are becoming commercially minded. You are speaking the language of the business. People will congratulate you on this. Some of them will use the word journey.
The Monday Problem
Two things on your list.
The first produces a number. Tune it, measure it, slide by Thursday, well done in the team call, small warm feeling that lasts until roughly Friday lunchtime.
The second prevents something. Do it properly and nothing happens. Nothing happening produces no number, no slide and no well done, because nobody has ever thrown a party for an outage that did not occur. There is no cake. If there were a cake it would say NOTHING HAPPENED and everybody would find it deeply unsettling.
Do not do it, and something breaks in about seven months, by which point nobody alive will connect the two events.
You know which one you pick now.
You did not always.
The Year the Dashboard Was Greenest
I worked with a team who hit every savings target they were given, four quarters running. Every number moved the right way. There was a slide. The slide was accurate. Nobody was fiddling anything and I want that clearly understood.
In the fifth quarter something broke and took the order system down for most of a working day.
When they finally added it up, that one day cost more than everything the four quarters had saved.
Sit with the uncomfortable part, because it is not the part you expect. Nobody did anything wrong. Every decision across those four quarters was defensible on the morning it was made. They trimmed, consolidated and deferred, and every one of those had a figure beside it and a person who could be thanked for it by name.
The thing that broke was in the part of the estate that had never produced a number for anybody.
It Bills the Wrong Person
The other thing that bothered me took me much longer to work out.
Attribution is a lovely word. It sounds neutral. It sounds like the truth calmly arriving with a clipboard.
But when a query is expensive, the expense was almost always decided years earlier, in a meeting, by somebody who has since left the company and is now extremely happy somewhere else. A table got denormalised for a reason that made sense in 2019. A nullable column arrived under deadline. A vendor application generates that shape and nobody in your building is legally permitted to touch it.
Then a report appears with a dollar figure on it and a team’s name next to the dollar figure.
And that team cannot change a single thing about it.
I have sat in the room while that report was presented. I have watched people be held to account, very politely, for a decision made before some of them were hired. Nobody behaved badly. The number simply had to land on somebody, and it landed on whoever happened to be standing nearest the query.
The meeting in 2019 could not be invoiced. So you get invoiced.
The Test I Wish Somebody Had Given Me
You can reduce the cost of any query to zero by making it fail.
Go on. Try it. Nobody will thank you, but the dashboard will look magnificent.
That is not really a joke, it is a test, and I now run every metric through it. If there is a way to move your number in the right direction by making the system worse, then the number is not describing quality. It is describing something else entirely, and given enough quarters it will get precisely what it is describing.
Any number you can improve by making the system worse is not a measurement. It is an incentive.
What the Sixty Eight Percent Actually Bought
I do not want you leaving here thinking that week was wasted, because it was not, and this is the part that took me longest to make peace with.
That sixty eight percent bought a maintenance window that now finishes before the business opens instead of ninety minutes into the working day.
It bought an incident in November that did not happen.
It bought about three years of headroom on a machine that would otherwise have needed replacing sooner, which is real and valuable and is not money, and which I could not have explained to anybody at the time because I was too busy explaining forty thousand dollars.
Nobody thanked anyone for any of those three. They remain the most valuable things I did that year.
Know Which Currency You Are Working In
I am not telling you to refuse the language of money. That is a form of pride you genuinely cannot afford, and I have watched good careers stall on exactly that principle while their owners felt very noble about it.
Learn it. Speak it well. It opens doors that twenty years of wait statistics never opened for any of us, and it is not the money’s fault that it is more persuasive than we are.
Just stop believing it is the same thing as being good at your job.
Be bilingual. Report in their currency, decide in yours, and try very hard not to fall in love with the exchange rate.
And when the two disagree, which they will, notice which one you feel the pull to obey. That moment tells you more than the number ever will.
This is a large part of what I now spend my time on inside client environments, and it is why my Comprehensive Database Performance Health Check does not open with a spend report. It opens by working out which failures are already possible, what each one would actually cost if it arrived on a Tuesday, and which of them can be made impossible this month. Some of that eventually shows up on an invoice. Most of it never will, and it is still the part worth paying for.
The question of who holds the judgment when a confident number walks into the room runs through all thirty essays in my book AI: Nobody’s in There. But we’re still in here. All thirty are free to read at pinaldave.com.
If I could go back, I would answer that person in finance properly. I would tell them it came off no invoice at all. I would tell them it bought a quiet November instead, and that I did not yet have any way of putting a quiet November on a slide.
I still do not. I have simply stopped pretending that means it was worth nothing.
This was never a story about a number being wrong, it is a story about a number being so easy to love that it quietly started choosing my work for me.
Reference: Pinal Dave (https://blog.sqlauthority.com/), SQL Server Cost Optimization, X
