The number on the board report had been wrong for a year

Not every database disaster looks like a disaster. Some of them look like a number on a slide that everyone has trusted for a year.

This one was a services business. A figure on the monthly board pack, a key revenue number, came straight out of a database through a report nobody had questioned, because it had always just worked. Except a change upstream, months earlier, had quietly broken one of the joins, and the number had been subtly wrong ever since. Not wildly wrong. Wrong enough to matter, small enough to never trigger an alarm.

They found it by accident, the way these things are always found, when someone cross-checked against another source and the two would not reconcile. Then came the uncomfortable part: working out how long it had been wrong, what decisions had been made on it, and how to explain to a board that a number they had relied on all year had a quiet error in it.

Nothing had failed. No alert fired, because no alert watches for a report being confidently incorrect. The data had been telling a slightly false story for a year, in plain sight, to people who had every reason to believe it.

This is the risk people forget when they think about databases. It is not only that they stop. It is that they can keep running perfectly while quietly telling you something that is not true.

We run a free, read-only health check that looks at the health and integrity of the data underneath your reports, not just whether the server is up. Sometimes the most expensive failure is the one that never looked like one.