CREATE DECRYPTED FILE statement

CREATE DECRYPTED FILE newfile
FROM oldfile KEY key

FROM clause Lists the file name of the encrypted file.
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.
KEY clause Lists the key required to access the encrypted file. The key can be either a string or a variable name.

Use this statement when your database requires recovery and you need to create a decrypted copy of the database for support reasons. You must also use this statement to decrypt any database-related files such as the transaction log, transaction log mirror, or dbspaces.

The original database file must be strongly encrypted using an encryption key. The resulting file is an exact copy of the encrypted file, without encryption and therefore requiring no encryption key.

Note

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.

If a database is decrypted using this statement, the corresponding transaction log file (and any dbspaces) must also be decrypted to use the database.

If a database requiring recovery is decrypted, its transaction log file must also be decrypted and recovery on the new database is necessary. The name of the transaction log file remains the same in this process, so if the database and transaction log file are renamed, then you need to run dblog -t on the resulting database.

You cannot use this statement on a database that has table encryption enabled. If you have tables you want to decrypt, use the NOT ENCRYPTED clause of the ALTER TABLE statements to decrypt them.

Note

For databases created with SQL Anywhere 16 or later, the ISYSCOLSTAT, ISYSUSER, and ISYSEXTERNLOGIN system tables always remain encrypted to protect the data from unauthorized access to the database file.

This statement is not supported in procedures, triggers, events, or batches.

You cannot be connected to the database you are decrypting. 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.

Your ability to execute this statement depends on the setting for the -gu database option, and whether you have the SERVER OPERATOR system privilege.

None.

SQL/2008 Vendor extension.

The following example decrypts a fictitious encrypted database called encContacts, and creates a new unencrypted database called contacts.

CREATE DECRYPTED FILE 'contacts.db'
FROM 'encContacts.db'
KEY 'Sd8f6654*Mnn';