RESTORE DATABASE filename
FROM archive-root
[ CATALOG ONLY 
   | [ RENAME dbspace-name TO new-dbspace-name ] ... ]
[ HISTORY { ON | OFF } ]
[ KEY encryption-key ]

filename : string | variable 
archive-root : string | variable 
new-dbspace-name : string | variable 

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:

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.

The permissions required to execute this statement are set on the server command line, using the -gu option. The default setting is to require DBA authority.

This statement is not supported on Windows Mobile.

None.

• Predefined dbspaces
• BACKUP statement
• Backup and data recovery
• SALOGDIR environment variable
• FREE PAGE ELIMINATION clause, BACKUP statement
• -gu dbeng12/dbsrv12 server option
• Progress connection property
• progress_messages option

The following example restores a 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'
FROM '\\\\.\\tape0';