If disk sandboxing is enabled, then the database's operations are limited to the directory where the main database file
is located. See Disk sandboxing.
CATALOG ONLY clause
Retrieves information about the named archive, and places it in the backup history file (backup.syb), but does not restore any data from the archive.
Allows you to specify a new location for each dbspace. You cannot use the RENAME clause to change the dbspace name. However,
you can use the RENAME clause to change the file name.
Allows you to control whether the RESTORE DATABASE operation is recorded in the history file, backup.syb.
Allows you to specify the encryption key to restore an archived strongly encrypted database that was backed up with free
page elimination on. If the back up was made with free page elimination off, then you do not need to specify the encryption
key to restore the database. The key can be either a string or a variable name.
As of version 12, you cannot restore archive backups created with version 11 or earlier database servers.
Unless HISTORY OFF is specified, each RESTORE DATABASE operation updates a backup history file called backup.syb. This file records the BACKUP and RESTORE operations that have been performed on a database server. You may want to prevent
the RESTORE DATABASE operation from being recorded in backup.syb if the following conditions apply:
your RESTORE DATABASE operations occur frequently
there is no procedure to periodically archive or delete the backup.syb file
disk space is very limited
If disk sandboxing is enabled, then the database's operations are limited to the directory where the main database file is
located. See Disk sandboxing.
RESTORE DATABASE replaces the database that is being restored. If you need incremental backups, use the image format of the
BACKUP command and save only the transaction log; however, image backups to tape are not supported.
During the execution of this statement, you can request progress messages.
You can also use the Progress connection property to determine how much of the statement has been executed.
You cannot be connected to the database you are restoring. You must be connected to a different database. For example, connect
to the utility database. The database that you are encrypting must not be running.
This statement is not supported on Windows Mobile.
The following example restores a fictitious database from a tape drive. The number of backslashes that are required depends
on which database you are connected to when you execute RESTORE DATABASE. The database affects the setting of the escape_character
option. It is normally set to On, but is set to Off in utility_db. When connected to any database other than utility_db, the
extra backslashes are required.
RESTORE DATABASE 'd:\\dbhome\\mydatabase.db'