Compare by table and key
Run source-to-target comparisons that show which tables match, which rows differ, and where cutover risk is concentrated.
MySQL Drift Detection
Validate MySQL source and target drift before cutover.
Drift detection is the step that turns a migration from hope into evidence. Cupcake DRCP helps teams compare source and target data, isolate row differences, and decide what must be repaired before traffic moves.
Why It Matters
Turn database movement into an operating workflow.
Separate drift from noise
Use recent CDC health, row activity, and compare timing together so teams understand whether differences are expected, stale, or dangerous.
Keep a cutover receipt
Preserve comparison results and follow-up repair actions so the migration decision has a traceable record.
Product Workflows
Related Cupcake DRCP screens.
Checklist
How to validate source and target drift
Step 1
Freeze the cutover scope: identify the tables and keys that must agree before promotion.
Step 2
Confirm snapshot completion and CDC catch-up before treating compare output as final.
Step 3
Run compare on high-value tables first, then broaden to supporting tables.
Step 4
Review row-level differences and choose whether to repair, accept, or delay cutover.
Step 5
Re-run compare after repair so the final decision uses fresh evidence.
Community Discovery
Useful MySQL operations topics to keep exploring.
FAQs
Quick answers.
When should drift checks run?
Run them after the snapshot baseline, during CDC catch-up, and again near cutover for the tables that matter most.
Is drift always a blocker?
No. Some drift may be expected during active writes, but unresolved differences in cutover-critical tables should be reviewed before promotion.