Real Estate Schema Migration Verification Checklist

Role: Senior Database Administrator specializing in high-concurrency property management and ERP databases.

Context

• Database Platform: {{source_db_engine}}
• Target Application: {{property_platform_name}}
• Release Target: {{migration_target_version}}
• Maintenance Window: {{maintenance_window_minutes}} minutes
• Affected Critical Tables: {{high_traffic_tables}}
• Staging Verification Host: {{staging_environment_url}}

Task

Generate an exhaustive pre- and post-deployment checklist to verify schema migrations for {{property_platform_name}}, ensuring zero data corruption across {{high_traffic_tables}} within the {{maintenance_window_minutes}}-minute window.

Method

1. Analyze DDL scripts targeting {{source_db_engine}} for table locks, column defaults, and foreign key constraint validations.
2. Review column type alterations on {{high_traffic_tables}} to detect implicit casting risks or table rewrites.
3. Verify index creation strategies to ensure all new indexes are constructed concurrently without locking write traffic.
4. Audit backfill queries on {{staging_environment_url}} to evaluate batch size limits and transaction log growth.
5. Check compatibility of view definitions, stored procedures, and triggers against version {{migration_target_version}}.
6. Formulate precise rollback steps for every atomic migration statement in the release sequence.
7. Establish replication lag checkpoints to ensure standby replicas remain synchronized during migration execution.

Constraints

• MUST include explicit validation queries for every item on {{high_traffic_tables}}.
• MUST NOT allow non-concurrent index operations or blocking table rewrites during execution.
• Items must be prioritized into Pre-Migration, Execution, and Post-Migration phases.
• Time budgets for each verification phase MUST sum to less than {{maintenance_window_minutes}} minutes.

Output format

Provide a structured markdown checklist organized into three distinct sections: '1. Pre-Deployment Validation', '2. Live Migration Steps', and '3. Post-Deployment Verification'. Each check must contain a status checkbox, verification command or query, and failure mitigation action. Total output should contain between 15 and 20 discrete check items.

Self-review

• Confirm all {{high_traffic_tables}} are explicitly addressed in validation queries.
• Verify all non-blocking constraints are strictly enforced for {{source_db_engine}}.
• Ensure rollback triggers are defined for every failure condition.