Skip to content
Log in

Database Migration Plan

Plans a schema change that ships without downtime, in steps that are each independently safe and reversible.

0

Share this prompt

Free — no card needed

Create a free account

to open Database Migration Plan — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCodingForDevelopers, OperatorsTested onClaudeChatGPT

Running it, start to finish

  1. Describe the change with real table sizes and write volume.
  2. Deploy each step separately, verifying between.
  3. Stop at the point of no return and confirm before proceeding.

What you get back

The output this produces, every time.

  • Starts from which application versions must coexist with which schema states.
  • Names the operations that lock dangerously at your data size, which is where staging-clean migrations fail.
  • Marks the point of no return as a decision rather than something discovered.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Give it real table sizes. Section 3 is entirely dependent on them. A migration that is instant at 10k rows can hold a lock for minutes at 10 million.
  • Watch replication lag during backfill. A batched backfill that outruns replication takes down read replicas, which is usually where your traffic is.
  • Check every intermediate state is overnight-safe. Section 7 matters because migrations get interrupted. A plan only safe when completed in one sitting is not a plan.

More Coding prompts

All Coding

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.