|
Is it possible to change a database from having no encryption to having simple encryption using the CREATE ENCRYPTED FILE command? Or must you use dbunload or dbinit flags and create a new database file? |
|
Starting with 11.0.1, you can use the CREATE ENCRYPTED DATABASE statement to create a new database (with all necessary files) from a not encrypted (or differently encrypted one). That does not require a reload. As to the docs, that does also allow to change from no encryption to simple encryption. EDIT 1: To answer your actual question, the same should be possible in older versions with CREATE ENCRYPTED FILE (so you should not need to do an unload) - but you have to take care to adapt all necessary files yourself. EDIT 2: As Graeme has pointed out, CREATE ENCRYPTED FILE does not support simple encryption. So I stand corrected... 2
Just to clarify - no, you cannot use
(15 Nov '11, 19:28)
Graeme Perrow
|
The description of the statement is that the CREATE ENCRYPTED FILE statement will create a new file and it does not replace the previous version of the file.
"You can also encrypt an existing database or change an existing encryption key by unloading and reloading the database using the dbunload -an option with either -ek or -ep".
HTH
As always, telling the version (and build) is quite helpful:)
Thanks for the information guys. We are using SQL Anywhere Network Server Version 10.0.1.3831.
To sum up:
With v10.0.1, I would conclude that the answer is: "Unfortunately no, you will have to use an unload", as