MySQL automation, with a reviewable outcome.

Automate the database checks you already understand.

Start with a manual comparison that answers a clear question: does the reporting target contain the expected rows, or has a replication target drifted from its source? Save the connections, table pairs, filters, and column mappings in a reusable plan.

Once the scope and outcome are understood, schedule that comparison. This gives recurring work the same context as a manual run and provides a history to inspect when a difference first appears. Use it alongside MySQL CDC to check the data that a stream is keeping up to date.

Choose how much repair to authorize.

A scheduled comparison can surface drift without making every difference an automatic write. If you enable policy-based repair, review the eligible tables, delete behavior, and row ceiling before letting the job run unattended.

For example, a small reference table may have a tightly bounded repair policy, while a business-critical table may require a person to review the findings. Choose limits from the actual data and operational requirements. Reassess the policy if the source, target, or mapping changes.

The MySQL comparison and repair guide explains how to inspect row differences, preview the proposed work, and export SQL for review.

Inspect what ran, not just what was scheduled.

1. Establish a manual result. Run the intended comparison and resolve mapping or access errors.
2. Set a schedule. Choose a cadence appropriate to the source workload and the freshness you need.
3. Review repair policy. Decide whether the schedule should only compare or also perform authorized repair within its limits.
4. Check the history. Review completed, failed, and missed work. Investigate recurring drift before expanding automation.

How is this different from the MySQL Event Scheduler?

The MySQL Event Scheduler runs scheduled SQL statements inside MySQL. Cupcake schedules application workflows built around saved source and target plans, data comparison, and repair policy. Choose the tool based on the work you need to repeat.

Choose where scheduled work should live.

Mac schedules require a paid license. The local engine runs while the Mac is awake and the operator is logged in; start-at-login and catch-up behavior do not make it run while asleep or logged out.

For work that needs a server operating model and team access, explore MySQL automation in the Enterprise Linux console. Desktop and Enterprise are separate products with separate licenses.