Plan expand-contract schema migration
Prompt that plans expand-contract schema migration with dual-write and a safe contract phase. Paste it into an AI tool of your choice, which then plans expand-contract schema migration.
- Topic
- Apps & prototypes
- Type
- Prompt
- Level
- Intermediate
- Time
- about 15 min
Results depend on the tool, the model and what you enter.
Result preview
Example: written by our editors, not real AI output.
Change: rename user.email → user.mail Expand: add mail, dual-write both Readers: API v2 first, BI last Contract: drop email when read=0 for 7 d Abort: if dual-write lag > 2 min
Fill in
What you type stays in this browser window. We store and send nothing.
- rename field
- split table
- new required field
- type widen
- mixed
- API
- workers
- BI export
- mobile old app
- mixed
- one service
- many services
- batch jobs
- partners
- mixed
Your prompt
You have edited the prompt. Changes in the fields above no longer overwrite it.
This is an instruction for an AI, not the result itself.
Where this prompt works
These AI tools are a good fit for this prompt:
How to use it
- Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
- Copy the finished prompt into an AI tool of your choice.
- Paste schema diff and consumer list, without production rows.
Why does this work?
Dropping the old column before every reader moves is a cutover, not expand-contract. Expand first.
Tips
- Keep a feature flag or config for dual-read until metrics prove the old path is idle.