Why use One-Click SQL Restore instead of RESTORE command?
Because One-Click SQL Restore is much faster. It unzips the bak file if necessary,
it connects to the SQL server on the start, it selects the right database, it is
smart enough to restart the server to drop open connections if necessary - all you
have to do is to press "Restore" button.
One-Click SQL Restore is most useful if you restore often. If you are a developer
that needs to restore databases a number of times - it will save you tons of time.
However it won't replace the RESTORE command in a complicated restore scenario.
Let's say you want to restore a backup created using MySqlBackupFTP
or BACKUP DATABASE command
- Double-click a *.bak file, or drag-and-drop *.bak or *.zip file onto One-Click SQL
- Select a Target database or type a new name
- Press "Restore" button
Q: Can I restore not only full, but also differential backups?
A: No. Only Full. Use
RESTORE for diff backup restore.
Q: I need other options: transaction log restore, file restore,
snapshot, restart, etc?
RESTORE command instead. One-Click SQL Restore should be used in simple
Q: Do you overwrite the files when restoring to another database?
A: When restoring a backup from database X to database Y,
we use "MOVE" option so Y files get overwritten.
Q: Restore errors
A: Most common errors are "The media family on device .. is incorrectly formed", "RESTORE HEADERONLY is terminating abnormally", "The backup of the system database on device .. cannot be restored because it was created by a different version of the server" - they all occur when you try to restore to an older SQL server. You can NOT restore backups from a newer SQL version to an older - the formats of
(Microsoft) backup files are different. See our
post on this.
Q: Does it have Command Line Interface?
A: Yes. Usage:
SqlRestore <backup file (.bak or .zip)> [options]
-run - runs the program in automatic (console) mode
-db <target database> - a target database where the backup file will be restored
-srv <QL Server name> - SQL Server instance name
-usr <SQL Server user name> - SQL Server user name (if not specified, then
Windows Authentication will be used)
-pwd <user password> - SQL Server user password (if not specified, then emptypassword
will be used)
-help or -? shows this help
Q: Do you guarantee the safety of the data?
A: No (nobody would). Under no circumstances we accept any
responsibility for the use and performance of this program. It is provided to you
"AS IS" - use at you own risk (See EULA). In general,
database backup and restore operations should only be handled by a person who knows
what he is doing. It is very easy to overwrite an existing database and loose the
data. If in any doubt - don't do it yourself, find a professional that could
Q: What license is it under?
A: It is a freeware - free of charge even
for commercial use, you can install it on any number of systems, you will not have
any proprietary rights, you can distribute it as long as you don't make money, you
can not make it part of your program. See full freeware license
Q: Where can I get support?
A: Only through the
forum. Please DO NOT email us for One-Click SQL Restore support - emails
will be unanswered. It is a free product.