Nobody will sign off the downtime, so the downtime signs itself off

You have asked three times. The patch is overdue, the maintenance is overdue, and every time you raise it the answer is the same. Not this month. We cannot take that system down right now. There is a launch, a close, a busy season, always a reason. So the window keeps slipping, and the work that needs it keeps not happening, and you are the one whose name is on it.

Here is the thing to say back, and it is not a technical thing. A maintenance window is not downtime you are asking for. It is downtime you are choosing, while it is cheap, instead of downtime that gets chosen for you later, while it is expensive. The system will come down. The only question is whether it comes down at 10am on a Sunday you planned, or at 2:39am on a night nobody picked. One of those you control. The other one controls you.

Your boss does not refuse the window because they think the risk is fine. They refuse it because the window has a cost they can see, an hour where the system is off, and the risk has a cost they cannot. So make the invisible side visible. Put a number on it. Work out what an hour of that system being down costs during business hours, against a planned hour at the quietest point of the week. The planned hour is almost always a fraction of the unplanned one, and it is the same hour, just on your terms.

Then take the choice off your own desk. Do not walk in asking for permission. Walk in with the two options written down. Option one, we take ninety minutes on a Sunday next month and this is closed. Option two, we keep deferring and accept that the timing is no longer ours to pick. Let them choose. A manager who refuses to schedule maintenance has, on paper, chosen option two, and most people will not sign their name to that once it is written down plainly in front of them.

The quiet part is that the system has usually been asking for this window for a while. The slow creep, the thing that needs a restart more often than it used to, the update that has been pending so long everyone stopped noticing. None of that fixes itself. It waits until the day it stops waiting, and that day is rarely a convenient one.

If you want the evidence to take upstairs, we can give it to you. We run a free, read-only SQL Server health check, fifteen minutes, no changes to anything, no sales call chasing you afterwards. You get a graded report in plain English that says what is at risk and why the maintenance matters. Hand that across the desk, and the window stops being your opinion and starts being a decision someone has to make.