Don’t let Lucy pull the football

By Brian Fitzgerald

Every October, Charlie Brown takes a run at the football, and every time, Lucy pulls the football away at the last second.

Year-end database changes can feel the same way. We prepare a change, line up the window, and take our run at it. Then, at the last minute, the change is postponed. A question nobody answered, a concern nobody addressed, or a feeling that now is not the right time is enough to stop the change that you planned. Once a change slips into November, the holidays and the freezes tend to carry it into next year. And the cost of a cancellation reaches well beyond the calendar.

The idea is simple: prepare your changes carefully, answer the concerns before anyone raises them, and finish them by the end of October.

Why October

October is unique. It is the last month when a major migration can still be completed with certainty. November and December bring year-end processing, change freezes, and vacations, and the people you would call for help may not be at their desks.

That makes October a sweet spot with a sharp edge. A minor postponement costs a couple of weeks provided a fallback window exists; otherwise, any hesitation costs the year.

What a cancellation costs

A canceled change rarely just moves to a new date. It leaves a mark, and that mark is why this post exists.

The cancellation reflects on everyone involved. A cancellation reflects on the DBA who owned the change, the DBA team, the infrastructure group, and the IT department as a whole, even if the team did everything right. People tend to remember that a change did not happen long after they have forgotten why.

The second approval is harder than the first. The questions raised before a cancellation do not go away. A do-over must answer them all, along with the new doubt the first attempt left behind. Expect more reviewers, more justification, and more time.

The plan itself may be reconsidered. Once doubts are in the air, the organization may step back and rethink the whole approach. It might bring in an outside consulting firm. It might defer the work indefinitely, or decide to move to a SaaS offering instead. Any of these can be a reasonable decision on its own, but none of them is the plan you prepared.

The people may change. Delay gives time for turnover. The leaders who understood the change and approved it may move on. Their successors will have their own priorities and may not have the same technical background or familiarity with the team’s work. You may need to make the case again from the beginning to people who were not there the first time.

That is why a postponement costs far more than a few weeks, and why you must prevent one.

Be a running back

Charlie Brown is a place kicker. A place kicker depends on someone else to hold the ball and hopes it will still be there when he arrives. A running back takes the ball and carries it down the field. Be proactive with your changes. Do not wait for the approval meeting to learn what the concerns are; find them first. Run around the defenders where you can, and where you cannot, be prepared to knock down every objection that stands between your change and the goal line. Don’t be a place kicker, be a running back.

Finish by October

Working backward from the end of October helps. Look at the changes you still hope to make this year, and ask which ones you can prepare, test, approve, and complete in the next few weeks.

Those are your changes for this year. Schedule each one for early October. Do this early, while calendars are still open and colleagues are still available to review your plans.

The rest can wait for January. That is not a failure. A change that is moved to a calmer season, with good preparation behind it, is a sound decision. A change that is rushed into a crowded December is the football Lucy is holding.

A calmer year-end

Charlie Brown keeps running at that football because he is an optimist, and optimism is a fine quality in a DBA. Optimism alone, however, does not get a change approved and completed. Preparation does.

Carry the ball. Finish the work while October is still here. When the holidays arrive, you can enjoy them, knowing your systems are steady and your changes are behind you.