Start from evidence
Repair begins from a compare result so operators know exactly which rows and tables are in scope.
MySQL Compare and Repair
Compare MySQL data, preview repairs, and reconcile drift safely.
Cupcake DRCP connects the compare result to the repair workflow: find drift, inspect the scope, dry-run the reconcile plan, then apply a controlled fix with an audit trail.
Why It Matters
Turn database movement into an operating workflow.
Preview before writes
Dry-run reconcile actions before target data changes, with row-count ceilings and typed confirmation for sensitive operations.
Audit the outcome
Keep compare, dry-run, confirmation, and repair history together so recovery teams can explain what changed.
Product Workflows
Related Cupcake DRCP screens.
Checklist
Safe compare-and-repair workflow
Step 1
Run compare and confirm the result is recent enough for the decision being made.
Step 2
Filter repair scope to the tables and rows that should be reconciled.
Step 3
Dry-run the repair and review row counts before applying changes.
Step 4
Use operator confirmation for target writes and keep the repair receipt.
Step 5
Run a follow-up compare to confirm the target now matches the source.
Community Discovery
Useful MySQL operations topics to keep exploring.
FAQs
Quick answers.
Can repairs be limited by scope?
Yes. The repair workflow should be constrained by table, row, compare result, and operator policy.
Why dry-run before repair?
Dry-run previews help teams catch surprising row counts or unintended scope before any target writes happen.