DbDefence Encryption Tools
Our encryption software uses highly optimized AES encryption routines to take full advantage of the benefits of multiprocessing. You can encrypt using 3 available methods:
Free Version can be used in commercial projects freely. However, the Free Version has a limited database size of up to 200 Mb. Read more about obtaining the full version.
Before encrypting any of your databases, it is highly cautioned that you create a complete backup of the database to ensure that your data is not lost in the event that there are any problems from the encryption or decryption process.
You may encrypt database files with or without access restrictions. By default, Encryptor GUI encrypts with access restrictions.
- If you encrypt with restriction access, database files are encrypted and the database becomes unavailable FOR ALL APPLICATIONS until application executes special SQL statement with the password.
- If you encrypt without restriction access, database files are encrypted, but it still can be accessed like in normal database.
Encryption process with the GUI
Encryptor GUI encrypts all files within the database. Typical database archives contain one .mdf file and one .ldf file. However, bigger databases can have several relevant log files and additional data files. DbDefence encrypts each file and each file is given an associated encryption key file. These files need to remain in the same location within the database. Do not delete or copy the mentioned log files if you transfer the database to a new location or server!
If you have a UAC enabled operating system (Vista and above) you will get warnings about escalating permissions. Higher access levels for those tools are necessary to modify database files. During the encryption process, the database will be detached from the server. So it is important to close all connections to that database. After the detachment, the files will be encrypted and reattached to the SQL Server.
Here is the successful encryption screenshot. As you can see, a small database, several megabytes in size, can be encrypted very quickly.
After the encryption, the GUI runs simple test to ensure the database functionality and data protection integrity. If this test fails, please contact us. We will be happy to help you on this matter.
If your database is part of complicated infrastructure, you may want to use exceptions to provide unconditional access to the objects. You can read more about that in the exceptions section of this manual.
Encrypted databases contain special keys called dbdx, which need to be opened to unlock future access to your database. You can read more about that here.