War story

The month-end report that brings the whole server to its knees

· Adrian Sullivan

Every business has a report that everyone dreads running. It is usually month-end, or year-end, or the big board pack, and when it runs, the database slows to a crawl and everyone else’s work grinds with it. People have learned to schedule around it. Do not run anything important while finance is closing the month. That has just become how it is.

It does not have to be how it is. That report is slow for a reason, and the reason is almost never that the data is too big. It is a query written years ago, by someone long gone, that was fine when the table had ten thousand rows and is now reading ten million every time it runs, the hard way, because nobody ever went back to it.

I have watched a report that took forty minutes and pinned the server come down to under a minute after an afternoon of work. Not magic. One index, one rewrite, a look at what it was actually doing. The business had spent two years scheduling their entire month around a problem that was a Tuesday’s work to fix, because everyone assumed slow was just the cost of a big report.

The tell is always the same. Everyone knows about it. Everyone has adapted to it. Nobody has measured it, because it has never quite been bad enough to stop everything, only bad enough to cost a little, every month, forever.

We find these, for free, read-only, and tell you which of your slow, dreaded, worked-around problems are actually a quick fix. Most of the time the server has been showing exactly what is wrong the whole time. Someone just has to look at the right thing.

Free health check

Want to know if this is sitting in your estate? We run a read-only check and hand you a graded report in plain English.

Get your free health check

← All posts