You have the date circled. The big sale, the launch, the end of the financial year. Marketing has known for months. Finance has known for a year. The whole business is pointed at one window where traffic, orders and reporting all peak at once. Here is the uncomfortable part. The one system everyone is about to lean on hardest, the database underneath it all, was probably sized for an ordinary Tuesday. It has never once been tested against the day you have all been planning for.
This is not a surprise that arrives. It is a surprise you scheduled. The load is not random. It is the most predictable spike of your year, and you can name the exact hour it will start. A spike you can see coming is not a risk in the usual sense. It is a decision you are making by not making it. The question worth sitting with is whether anyone has actually proven the database will hold, or whether everyone is quietly assuming it because it held last year at half the volume.
Would it be unreasonable to ask, before the day, whether your busiest hour has ever been rehearsed? Most boards have never put that question to anyone. The answer tends to be a pause, then a confident sentence with no test behind it. The database does not run on confidence. It runs on connections, on memory, on a few queries that are fine at normal load and fall off a cliff when ten times the orders hit them at once. Those queries do not warn you politely. They were saying it the whole time, in numbers nobody was reading, that they had a ceiling.
When this goes wrong it rarely looks like a clean crash. It looks like the site slowing to treacle at the worst possible minute. Carts fail. Customers refresh and give up. Your best sales day turns into a public one, in front of the exact audience you spent the marketing budget to attract. The cost is not just the lost hour. It is the orders that never come back, and the reputation you cannot un-spend. The technical fault is small. The business loss is not.
So here is the calibrated question for your team. How would we know, today, that the database can carry the day we have all circled? Not an opinion. Evidence. If the honest answer is that no one has checked the system against the peak it was built around, that is the gap, and it is cheaper to find now than at the till. You do not need a project to find out. You need someone to look.
We will do that look for free. A read-only, 15-minute health check of your SQL Server, run by a person, with no changes to anything you run and no sales follow-up unless you ask for one. You get back a graded report in plain English that tells you where the weak points are before your busiest day finds them for you. NZ-based, doing this since 2018. If you have a date circled, have it checked before the date arrives.
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