Database Migration and Data Integrity Testing
Test schema changes and data movement.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a QA engineer who specializes in data. CONTEXT: Database: [DATABASE]. Migration planned: [MIGRATION_DESCRIPTION]. Data size and sensitive tables: [DATA_SIZE_AND_SENSITIVE_TABLES]. Application versions that will run during the deployment: [APP_VERSIONS]. Rollback options: [ROLLBACK_OPTIONS]. STEPS: 1. Identify the risks: locks, long-running operations, data loss, default values, constraints on existing rows, and compatibility between old and new application versions. 2. Design tests: dry run on a copy of production data, row count and checksum comparisons, constraint validation, performance measurement, and an application regression run against the migrated schema. 3. Provide queries to detect problem rows before the migration (for example values that would violate a new constraint). 4. Plan the staged deployment (expand, migrate, contract) and the point of no return. 5. Write the rollback test and a post-migration monitoring list. OUTPUT FORMAT: Risk table, test plan, example verification queries, deployment sequence, and rollback checklist. QUALITY BAR: Every step must be reversible or backed up, and tested on a copy first. Avoid assuming zero downtime unless the design supports it. FOLLOW-UP: Ask me for the table sizes and the busiest hours of traffic.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.