Last updated: 2026-11-10
Backup & Restore
Protect your data with database backups and restore when needed. Jam SQL Studio supports SQL Server native backups, BACPAC export/import for Azure SQL, and PostgreSQL pg_dump/pg_restore operations.
Personal Mode Limits
In Personal mode, creating a backup is limited to source databases ≤ 1 GB. Restoring a backup has no size limit. Upgrade to Pro to remove the backup-creation limit.
SQL Server Backup
Create native SQL Server backup files (.bak) for your databases.
Creating a Backup
- Right-click your database in Object Explorer
- Select Backup Database (.bak)...
- Click Browse... to choose a server folder (or click Use server default / type a path)
- Choose backup type and compression
- Click Start Backup
A progress dialog shows the completion percentage while the backup runs. You can cancel the operation at any time.
Backup Options
| Option | Description |
|---|---|
| Backup Type | Full (complete database), Differential (changes since last full), or Transaction Log |
| File Path (SQL Server) | Server-side file path for the .bak file. Click Use server default to prefill the SQL Server instance default backup folder, or Browse... to select a folder (if permitted). |
| Compression | Enable backup compression to reduce file size (requires SQL Server 2008+) |
Backup Types Explained
- Full Backup - Complete copy of the entire database. Start with this for any backup strategy.
- Differential Backup - Contains only data changed since the last full backup. Faster and smaller than full backups.
- Transaction Log Backup - Backs up the transaction log for point-in-time recovery. Requires database to be in Full recovery mode.
SQL Server Restore
Restore a database from a backup file.
Restoring a Database
- Right-click the Databases folder (or a database) in Object Explorer
- Select Restore Database (.bak)...
- Click Use server default / Browse... to select the .bak file on the SQL Server machine (or type the server path)
- Choose the target database name
- Configure restore options
- Click Start Restore
A progress dialog shows the completion percentage while the restore runs. You can cancel the operation at any time.
Restore Options
| Option | Description |
|---|---|
| Backup File Path (SQL Server) | Server-side file path to the .bak file. Click Use server default to start from the SQL Server default backup folder, or Browse... to select a file (if permitted). |
| Target Database | Name for the restored database (can be different from original) |
| Overwrite | Replace existing database with the same name |
| Recovery State | RESTORE (ready for use), NORECOVERY (for applying additional backups), or STANDBY (read-only with restore capability) |
Disconnecting while a backup or restore runs
A running backup or restore keeps running on the server when you disconnect, reconnect or remove the connection, and the progress dialog shows the result when it finishes. This holds for every SQL Server connection, including a Windows connection with the port left blank (the Port field shows <auto>) or with Windows authentication. Quitting Jam SQL Studio stops the backup or restore, as Cancel does. A connection through an SSH tunnel is the exception: disconnecting it closes the tunnel, and the backup or restore stops with it.
BACPAC Export/Import
BACPAC files are portable packages for migrating databases to Azure SQL or other SQL Server instances.
Export to BACPAC
- Right-click your database in Object Explorer
- Select Export Data-tier Application (.bacpac)...
- Choose where to save the
.bacpacfile in the save dialog - Wait for the export to finish in the export dialog
The export runs in SQL Tools Service, which reports no percentage for a BACPAC, so the dialog shows the elapsed time while it runs. When the export has finished, the dialog shows the file it wrote, the file size and how long the export took. If it fails, the dialog shows the error that SQL Server or DacFx reported, and Copy error copies that error together with the full report SQL Tools Service sent.
While the export runs, Cancel export stops it. Closing the dialog, or the minimize button, keeps the export running and moves it to the status bar at the bottom of the window (see Exports and imports in the status bar).
Import from BACPAC
- Right-click your connection in Object Explorer
- Select Import Data-tier Application (.bacpac)...
- Click Browse… to pick the
.bacpacfile, or type its path - Enter the name of the new database. Browse fills in the file name, and the dialog warns you if a database with that name already exists, because the import needs a new database.
- Click Import
When the import has finished, the dialog names the database it created and Object Explorer lists it. If the import fails, the dialog shows the error that SQL Server or SQL Tools Service reported, for example Msg 7609 … Full-Text Search is not installed together with the statement that failed, or Could not load package from '…'. Could not find file '…'. for a path that does not exist. Copy error copies that error together with the full report. Cancel import stops a running import; closing or minimizing the dialog keeps the import running in the status bar, as for an export.
An import that fails or is cancelled after SQL Server created the new database leaves that database on the server, with whatever was copied before it stopped. The dialog says so and names the database. Drop database… opens the same confirmation as running a destructive statement, with the exact statement and the connection, and drops the database only if you confirm. Nothing is dropped automatically, and the button is never offered for a database that existed before the import started.
Right before the drop, Jam SQL Studio checks that the database is still the one the import left. If it has been dropped, or dropped and created again, since the import stopped, nothing is dropped: the notice says why in a sentence and no longer offers Drop database…. If another import, clone or restore into the same database name on that connection starts while the notice is still shown (for example in the status bar's details), the button stays, but confirming it drops nothing: the notice says the database is no longer listed as left behind by the operation. If the check before the drop gets no answer within 10 seconds, or the drop statement fails, nothing is dropped, the notice shows the message (for example SQL Server's Cannot drop the database '…', because it does not exist or you do not have permission.), and you can try again.
An export or import that runs longer than 6 hours is cancelled, and the dialog says the app stopped waiting for it. If SQL Tools Service never reported the task, the app cannot cancel it, and the dialog says so.
Exports and imports in the status bar
A minimized export or import keeps its entry in the status bar at the bottom of the window, with the database name and the latest status. Show details (the expand button on the entry) opens its details. While the export or import runs, the details show the elapsed time and Cancel export or Cancel import.
Closing the details, with Close, the × or Escape, returns the entry to the status bar. A finished entry stays there until you dismiss it with its × or click Done in its details. The details of a failed export or import show the error with Copy error, and those of a failed import that left a partly created database show the same notice as the import dialog, with Drop database… and the connection's name. After the drop, Object Explorer lists the connection's databases again, and the details, opened again, say the database was dropped (or why it was not) instead of offering the drop.
BACPAC vs BAK Comparison
| Feature | BAK | BACPAC |
|---|---|---|
| Format | Native SQL Server | Portable package (schema + data) |
| Azure SQL Support | Limited (requires VM) | Full support |
| Speed | Faster | Slower (data validation) |
| Point-in-Time | Yes (with log backups) | No |
| Best For | Local backup/restore | Cloud migration, archiving |
PostgreSQL Backup
Backup PostgreSQL databases using pg_dump.
Creating a PostgreSQL Backup
- Right-click your PostgreSQL database in Object Explorer
- Select Backup Database (pg_dump)...
- Choose the backup format
- Click Start Backup
- Select a destination file when prompted
If the backup fails, the dialog shows the error lines pg_dump printed, and Copy error copies them together with everything pg_dump wrote to its error output.
Backup Formats
| Format | Extension | Description |
|---|---|---|
| Custom | .dump | Compressed binary format. Most flexible, supports selective restore. |
| Plain SQL | .sql | Human-readable SQL script. Can be edited, executed with any client. |
PostgreSQL Restore
Restore PostgreSQL databases using pg_restore.
Restoring a PostgreSQL Database
- Right-click your PostgreSQL database in Object Explorer
- Select Restore Database...
- Choose the target database name
- Configure restore options
- Click Select File & Restore and pick a .dump or .sql file when prompted
If the restore fails, the dialog shows the error lines pg_restore or psql printed, and Copy error copies them together with the tool's whole error output.
PostgreSQL Restore Options
- Create Database - Create the target database if it doesn't exist
- Drop Existing - Drop existing objects before restore
Backup Progress
Monitor backup and restore operations in real-time.
The progress dialog shows:
- Progress bar - Completion percentage, for operations that report one (SQL Server .bak backup and restore). BACPAC export and import show the elapsed time instead.
- Status messages - Current operation being performed
- Cancel button - Stop the current operation
- Error details - The error the server or tool reported, on failure. BACPAC export and import and PostgreSQL backup and restore add Copy error, which copies the full report
- Result - What the finished operation wrote or created
Best Practices
SQL Server
- Schedule regular full backups (weekly minimum)
- Use differential backups between full backups for large databases
- Enable backup compression to save storage space
- Test restores periodically to verify backup integrity
- Store backups on separate storage from the database
PostgreSQL
- Use custom format for production backups (most flexible)
- Use plain SQL format when you need to edit or review the backup
Azure SQL / BACPAC
- Use BACPAC for migrating to/from Azure SQL Database
- Validate data before export to ensure clean BACPAC files
- Consider Azure's built-in backup features for production Azure SQL databases
Frequently asked questions
How do I backup a SQL Server database in Jam SQL Studio?
Right-click the database in Object Explorer and select 'Backup Database (.bak)...'. Choose a folder on the SQL Server machine (Browse...) or click 'Use server default' / enter a server-side path, choose backup type (full, differential, or log) and compression, then click Start Backup.
What is the difference between BAK and BACPAC files?
BAK files are native SQL Server backups that include the full database state. BACPAC files are portable packages containing schema and data that can be imported into Azure SQL Database or other SQL Server instances. Use BAK for local backups and BACPAC for cloud migrations.
How do I restore a database from a backup file?
Right-click the Databases folder (or an individual database) in Object Explorer and select 'Restore Database (.bak)...'. Use 'Use server default' / Browse... to pick a .bak file on the SQL Server machine (or enter the server path), choose the target database name and restore options, then click Start Restore.
Can I backup a PostgreSQL database with Jam SQL Studio?
Yes. Right-click a PostgreSQL database and select 'Backup Database (pg_dump)...'. Choose Custom (.dump) or Plain SQL (.sql), then pick a save location when prompted. Jam SQL Studio uses pg_dump under the hood.
How do I export a database for Azure SQL?
Use the Export Data-tier Application (.bacpac) feature. Right-click your database, select 'Export Data-tier Application (.bacpac)...', then choose a destination file when prompted. The resulting .bacpac can be imported into Azure SQL Database.
Ready to Protect Your Data?
Download Jam SQL Studio and create your first database backup.



