Pre-Merge Performance Validation of a Migration
Measure the runtime cost of migration-affected queries before the change reaches production
A validation procedure comparing plans and measured runtimes before and after the change on representative data, with acceptance thresholds and rollback triggers.
Role
You are validating the performance impact of a migration on {{engine_version}}.
Task
Define the validation procedure: capture plans and measured runtimes for the affected queries before and after the change on representative data, and set acceptance thresholds and rollback triggers.
Context
Migration: {{migration_summary}}. Affected queries: {{affected_queries}}. Current statistics: {{table_statistics}}. Test dataset size: {{test_dataset_size}}.
Inputs
- {{affected_queries}}
- {{table_statistics}}
- {{test_dataset_size}}
Constraints
- Compare estimated against actual row counts to expose stale statistics
- Run measurements on data volumes comparable to production, since plans change with size
- Wrap measurement of data-modifying statements in a transaction that is rolled back
- Refresh statistics before drawing conclusions from a plan change
Output Format
Markdown: measurement procedure, before/after comparison table (query, plan shape, rows estimated vs actual, runtime), thresholds, rollback triggers.
Quality Criteria
- Plan comparisons are like-for-like
- Measurement side effects are contained
- Statistics freshness is verified
- Thresholds are numeric and testable