Backup / Restore

✓ functional

Back up and restore the database, with destructive steps scripted first for review.

Back up and restore the database. This was the first real Tools-menu admin dialog and set the template the rest follow: a focused form on the shared dialog chrome, with any destructive step scripted first for review rather than run on click.

On SQL Server, the dialog has Backup and Restore tabs over a live database dropdown and a path field that pre-fills a sensible .bak location. Backup offers Full, Differential, or Log, with Compression and Checksum on by default and Copy-only opt-in; Restore offers REPLACE (off by default) and RECOVERY (on). A preview pane shows the exact BACKUP / RESTORE T-SQL as you type, and Script to Editor hands it to a query tab - nothing runs from the dialog.

PostgreSQL and MySQL restore differently. Their Restore from file dialog drives pg_restore or the mysql client directly: it sniffs the chosen file to tell an archive from a plain SQL script, exposes the pg_restore flags (--clean, IF EXISTS, single transaction, --no-owner), shows the exact command line in a danger confirm before anything runs, streams per-object progress, and refuses production-marked connections outright.

SQLly Backup and Restore dialog — Backup / Restore: choose a backup or restore operation for the database; the resulting statement opens for review.