Plan this database migration step by step. Migration goal: {{migration_goal}} Current schema: {{current_schema}} Target schema: {{target_schema}} Table size: {{row_count}} rows Peak traffic: {{peak_qps}} QPS Think through systematically: 1. COMPATIBILITY: Is the change backward compatible? 2. MIGRATION STRATEGY: Expand-contract or big bang? Why? 3. DATA TRANSFORMATION: What data needs to be transformed? 4. ROLLBACK PLAN: How do we undo this if something goes wrong? 5. LOCKING IMPACT: Will any step acquire table locks? 6. BATCHING: Should we process in batches? What size? 7. VALIDATION: How do we verify data integrity post-migration? 8. PERFORMANCE IMPACT: What is the expected performance hit during migration? 9. EXECUTION TIMING: When should we run this? Maintenance window? 10. RUNBOOK: What are the exact steps with commands?
Database Migration Planning
Plan a complex database migration by thinking through each step.
70 copies0 forks
Share this prompt:
Details
Category
CodingUse Cases
Database migration planningSchema change workflowZero-downtime migration design
Works Best With
claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared