Backup / Restore
functionalBack 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.
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), and shows the exact command line in a danger confirm before anything runs. It streams per-object progress and refuses production-marked connections outright.
On ClickHouse the dialog scripts BACKUP DATABASE and
RESTORE DATABASE to the server's configured backups disk, server-side
statements, reviewed in a tab like the T-SQL ones.
Where an engine backs itself up some other way, the menu item says so instead of opening an empty dialog. SQLite and DuckDB databases are single files (copy the file, or run EXPORT DATABASE on DuckDB). A libSQL / Turso database is backed up from its server (Turso's own backups, or a copy of sqld's data directory). Oracle backups run through RMAN or Data Pump on the server, which SQLly does not drive yet. Redis snapshots itself with BGSAVE or BGREWRITEAOF, which you can run from a query tab.

