This statement decrypts strongly encrypted databases.
CREATE DECRYPTED FILE newfile
FROM oldfile KEY key
FROM Lists the file name of the encrypted file.
KEY Lists the key required to access the encrypted file.
This statement decrypts an encrypted database, transaction log file, or dbspace and creates a new, unencrypted file. The original 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.
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 will still be 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.
If you want to encrypt an existing database, you need to either use the CREATE ENCRYPTED FILE statement, or unload and reload the database using the dbunload -an option with either -ek or -ep. You can also use this method to change an existing encryption key.
You cannot use this statement on a database on which table encryption is enabled. If you have tables you want to decrypt, use the NOT ENCRYPTED clause of the ALTER TABLE statements to decrypt them. See ALTER TABLE statement.
This statement is not supported in procedures, triggers, events, or batches.
Must be a user with DBA authority.
SQL/2003 Vendor extension.
The following example decrypts the contacts database and creates a new unencrypted database called contacts2.
CREATE DECRYPTED FILE 'contacts2.db' FROM 'contacts.db' KEY 'Sd8f6654*Mnn';