Important Changes

What's new in DbDefence 7.4.1

  • Added support for databases with memory optimized tables.
  • Fixes installer on SQL Server 2017 LOCALDB.
  • Fixes issues with activation on cluster.

What's new in DbDefence 7.3.17

  • This build improves overall performance if all encrypted databases use Maximum transparency mode.

What's new in DbDefence 7.3.16

  • Fixed issues with FILESTREAM with large number of files.

What's new in DbDefence 7.3.10

  • Added compatibility with SQL Server 2014 SP2 CU12 (X64).

What's new in DbDefence 7.3.3

  • Fixed bug in backup system: In average aproximately 0.5% of backups were produced corrupted (not critically) since v.6.1. It is a good practice to verify backups with RESTORE VERIFYONLY command.
  • Fixed compatibility with SQL Server 2012 build 11.0.7462.6 (X86).

What's new in DbDefence 7.3.1

  • Added checks to encryption API.
  • Added function dbd_profiling to enable/disable profiling without re-encryption.
  • Fixed compatibility with SQL Server 2017 CU4 (build 14.0.3022).

What's new in DbDefence 7.3

  • New FIPS 140-2 validated module. Read more about this important change.
  • Fixed compatibility with SQL Server 2014 32-bit build 12.0.5571.0

What's new in DbDefence 7.1

  • Added support for SQL Server 2017.

What's new in DbDefence 7.0

  • Support for PKCS#11 Modules
  • Speed improvements for SQL Servers with large number of queries

What's new in DbDefence 6.5

  • Added not-exportable keys.
  • Added options in Encryption API to allow access by login and not-exportable keys.
  • Visual improvements in Encryptor GUI.

What's new in DbDefence 6.1

  • Added support for SQL Server 2016.
  • Added automatic access by login.
  • Improved performance.
  • Fixed several bugs.

What's new in DbDefence 5

  • Added support for SQL Server 2014.
  • Improved after-encryption tests.
  • Fixed several bugs.

What's new in DbDefence 4

The DbDefence 4 has several important improvements.

  • Client Program Configuration completely rewritten. You do not need to specify passwords in command line anymore. Once setup, the password is securely stored on the computer in encrypted form and neither viewable nor transferable. Read more.
  • The way how DbDefence loads itself into SQL Server process was also improved. Now it does not depend on renamed files in the Binn directly. That also simplifies distribution of encrypted data as a part of your installer.
  • Replication part was changed. If you used replication before, please check documentation. You will need to setup passwords manually. Previous version of software tried to do that automatically, but it often failed due to a SQL Server security restrictions.
  • DbDefence can be installed automatically in one command line. Read more.
  • Improved documentation on encryption with certificates.

Previously encrypted databases are fully compatible with the new version. If you have purchased copy of DbDefence 3, you may install new version over the old one. Your activation key will work if you ordered it less than a year ago.