Skip to main content
Backup and restore

Restore

Roll a schema back to a known-good state, with a preview and a dry run first.

Restore brings a schema back to the state captured in a backup. Because it is most often used under time pressure, every step is designed to be checked before it runs.

Restore from backup

orders_prod-20260714-2104.sql

RestorePreview changesCompare with live

Restoring replaces 3 objects that exist only in the live schema

A safety backup of the current state is taken first. Review the list below.

Object
orders.fulfilment_noteRemovedDROP
orders.statusModifiedREVERT
customersIdenticalKEEP
Dry run · 42 of 42 tables verified100%
Dry run completed · no errors reported
A restore preview, showing what would change before anything is applied.

Preview, dry run, then restore

  1. Preview

    SchemaSync compares the backup with the live schema and lists what restoring would add, change and remove. Objects that exist only in the live schema are called out separately, because those are what a restore would discard.

  2. Dry run

    Every object is verified without writing anything. This catches privilege problems and unsupported definitions before the real run.

  3. Restore

    A safety backup of the current state is taken first, so the restore itself can be undone.

Restoring a single object

A whole-schema restore is rarely what you want. When one routine was overwritten or one index dropped by mistake, select just that object and restore it alone — the rest of the schema is left untouched.