Separated key storage

Note: this functionality appeared in older version of DbDefence and may not be useful in recent versions. Instead, you can use key import

Since DbDefence v3.1 keys can be stored separately from database files. Keys can be stored anywhere on the filesystem or even on remote HTTP server.
When SQL Server with installed DbDefence opens database first it looks for key in the same folder with the database file. If there
is no key file it looks for path in the registry at HKEY_LOCAL_MACHINE\Software\ActivecryptSoftware\DbDefence\Keys\
and HKEY_CURRENT_USER\Software\ActivecryptSoftware\DbDefence\Keys\


Keypath2 633x245

Name of the database can be short name like on the picture or full path to the database file.

Important notes:

If you want to use HKEY_CURRENT_USER branch, note that SQL Server usually runs under Network Service or Local System accounts. If you start regedit as Administrator you can find corresponding profiles at HKEY_USERS\S-1-5-20 and HKEY_USERS\S-1-5-18
If you want to use HTTP path, do not forget to add http: or https: at the beginning.
Normally SQL Server not allowed to make outgoing connections. Please make sure that you have set appropriate permissions.