Skip to main content
Getting started

Your first comparison

Connect two databases and read the results, end to end, in about five minutes.

This walkthrough compares a development schema against a staging schema. Comparison is read-only, so it is safe to run against anything you have SELECT access to.

  1. Add two connections

    Open the connection manager and add your source and target. Give each one an environment label — production connections are shown in a distinct colour so they are hard to mistake for a sandbox.

  2. Select the schemas

    Pick a source schema and a target schema. They do not need to share a name; comparing orders_dev against orders_prod is the normal case.

  3. Compare

    SchemaSync reads both structures and reports every difference, grouped by object type. Nothing is written at this stage.

  4. Read the summary

    The strip above the results counts what is only in the target, only in the source, changed, and identical. Start with the changed objects — those are where surprises live.

  5. Open a difference

    Select any object to see both definitions side by side with the changed lines marked.

SchemaSync Professional

orders_dev ⇄ orders_prod

CompareFiltersSnapshotGenerate SQLBackup

Source

orders_dev

localhost:3306

Target

orders_prod

db-prod.internal:3306

12added4removed9modified148identical
Object
customers.loyalty_pointsAddedCREATE
orders.statusModifiedMODIFY
idx_orders_placed_atAddedCREATE
sessions.legacy_tokenRemovedDROP
fk_orders_customerModifiedREPLACE
vw_monthly_revenueAddedCREATE
paymentsIdenticalSKIP
MySQL 8.0.42 → MySQL 8.4.0 · 173 objects scanned
Comparison results, with the summary strip above the object list.

What the symbols mean

+ Added
The object exists in the target but not in the source.
− Removed
The object exists in the source but not in the target.
~ Modified
The object exists in both, with a different definition.
= Identical
No difference was found. Hidden by default once you apply a filter.

When you are ready to act on the results, continue to generating migration SQL.