CREATE DECRYPTED DATABASE newfile
FROM oldfile 
[ KEY key ] 

The CREATE DECRYPTED DATABASE statement produces a new database file (newfile), and does not replace or remove the original database file (oldfile).

All encrypted tables in oldfile are not encrypted in newfile, and table encryption is not enabled.

If oldfile uses a transaction log or transaction log mirror, the files are renamed newfile.log and newfile.mlg, respectively.

If oldfile contains dbspace files, a D (decrypted) is added to the file name. For example, when you execute the CREATE DECRYPTED DATABASE statement, if oldfile is mydbspace.dbs, newfile becomes mydbspace.dbsD.

You cannot execute this statement on a database that requires recovery. This statement is not supported in procedures, triggers, events, or batches.

DBA authority.

None.

• Encrypting and decrypting a database
• CREATE ENCRYPTED DATABASE statement
• CREATE ENCRYPTED FILE statement
• CREATE DECRYPTED FILE statement

The first statement below creates an AES256-encrypted copy of the demo.db called demoEncrypted.db,. The second statement creates a decrypted copy of demoEncrypted.db called demoDecrypted.db.

CREATE ENCRYPTED DATABASE 'demoEncrypted.db'
   FROM 'demo.db'
   KEY 'Sd8f6654*Mnn'
   ALGORITHM 'AES256';
CREATE DECRYPTED DATABASE 'demoDecrypted.db'
   FROM 'demoEncrypted.db'
   KEY 'Sd8f6654*Mnn';