How do I use the "Migrate Database Between Versions" prompt?

Copy the prompt template, fill in the variables (SOURCE_VERSION, TARGET_VERSION, DATABASE_TYPE, DATABASE_SIZE, CRITICAL_COMPONENTS, BUSINESS_CONSTRAINTS, DOWNTIME_TOLERANCE), and paste it into ChatGPT, Claude, or Gemini.

What AI tools work with this coding prompt?

This prompt works with chatgpt, claude, gemini. Simply copy and paste the template into any of these AI assistants.

Tips for getting the best results?

Always perform a full backup and verify restore capability before beginning migration Test the migration process on a copy of production data in a staging environment first Document all custom configurations and extensions that need to be migrated separately Plan for 2-3x the estimated migration time and have rollback procedures ready Monitor application logs closely for the first 48 hours after migration completion

coding advanced

Migrate Database Between Versions

Generate comprehensive database migration plans with version compatibility checks, data mapping, and rollback strategies for safe upgrades.

Works with: chatgptclaudegemini

Prompt Template

You are a senior database administrator tasked with creating a comprehensive migration plan for upgrading from [SOURCE_VERSION] to [TARGET_VERSION] for a [DATABASE_TYPE] database. Database context: - Current version: [SOURCE_VERSION] - Target version: [TARGET_VERSION] - Database size: [DATABASE_SIZE] - Critical tables/schemas: [CRITICAL_COMPONENTS] - Business constraints: [BUSINESS_CONSTRAINTS] - Downtime tolerance: [DOWNTIME_TOLERANCE] Provide a detailed migration plan that includes: 1. **Pre-migration Analysis** - Compatibility assessment between versions - Deprecated features and breaking changes - Performance impact evaluation - Resource requirements (CPU, memory, storage) 2. **Migration Strategy** - Recommended migration approach (in-place, side-by-side, or hybrid) - Step-by-step migration sequence - Data transformation requirements - Index and constraint handling 3. **Risk Assessment & Mitigation** - Potential failure points - Data integrity safeguards - Performance degradation risks - Rollback procedures and triggers 4. **Testing Plan** - Pre-migration testing checklist - Validation queries for data integrity - Performance benchmarking approach - User acceptance testing guidelines 5. **Implementation Timeline** - Detailed timeline with milestones - Resource allocation - Communication plan - Go-live criteria 6. **Post-Migration Activities** - Monitoring and alerting setup - Performance optimization tasks - Documentation updates - Team training requirements Include specific SQL commands, configuration changes, and monitoring queries where applicable. Emphasize safety measures and provide clear rollback instructions for each major step.

Variables to Customize

[SOURCE_VERSION]

Current database version to migrate from

Example: MySQL 5.7

[TARGET_VERSION]

Target database version to migrate to

Example: MySQL 8.0

[DATABASE_TYPE]

Type of database system

Example: MySQL

[DATABASE_SIZE]

Size and scale of the database

Example: 500GB with 50M records across 200 tables

[CRITICAL_COMPONENTS]

Most important database components that cannot fail

Example: user_accounts, transactions, inventory tables

[BUSINESS_CONSTRAINTS]

Business limitations and requirements

Example: 24/7 operation, peak hours 9-17 EST, compliance with SOX

[DOWNTIME_TOLERANCE]

Acceptable downtime window

Example: Maximum 2 hours during weekend maintenance window

Example Output

# MySQL 5.7 to 8.0 Migration Plan ## Pre-migration Analysis **Compatibility Issues:** - PASSWORD() function deprecated - update authentication - sql_mode changes require application testing - utf8mb4 is now default charset **Resource Requirements:** - 50% additional storage during migration - 8GB RAM minimum for upgrade process - Estimated 4-6 hours for 500GB dataset ## Migration Strategy: Side-by-Side Approach 1. **Phase 1:** Setup MySQL 8.0 on secondary server 2. **Phase 2:** Initial data sync using mysqldump with --single-transaction 3. **Phase 3:** Incremental sync using binary logs 4. **Phase 4:** Final cutover during maintenance window ## Risk Mitigation - Full backup verification before starting - Binary log retention for point-in-time recovery - Staged rollback plan with DNS switching ## Critical Validation Queries ```sql -- Data integrity check SELECT COUNT(*) FROM user_accounts WHERE created_at > '2024-01-01'; -- Performance baseline EXPLAIN SELECT * FROM transactions WHERE user_id = 12345; ``` ## Timeline - Week 1-2: Environment setup and testing - Week 3: Initial data migration - Week 4: Application testing and validation - Week 5: Go-live during weekend maintenance window

Pro Tips for Best Results

Always perform a full backup and verify restore capability before beginning migration
Test the migration process on a copy of production data in a staging environment first
Document all custom configurations and extensions that need to be migrated separately
Plan for 2-3x the estimated migration time and have rollback procedures ready
Monitor application logs closely for the first 48 hours after migration completion