Important Changes

Build 1243 (DLL ver. 10.0.6.1X )

  • Fixed compatibility with SQL Server 2022 CU12

Build 1239 (DLL ver. 10.0.5.1X )

  • Fixed compatibility with SQL Server 2022 with CVE-2024-0056 patch (build 16.0.1110)

Build 1237 (DLL ver. 10.0.4.1X )

  • Updated FIPS 140-2 module to certificate #4282
  • Binaries are signed with new EV certificate from Digicert

Build 1225 (DLL ver. 10.0.3.2X )

  • Added support for SQL Server 2022 CU8

Build 1215 (DLL ver. 10.0.2.14X )

  • Fixed bug related to masking appeared since build 1212.

Build 1214 (DLL ver. 10.0.2.12X )

  • Added support for SQL Server 2022 CU1
  • Added support for SQL Server 2016 with updates from 2023-02-14.
  • Fixed deadlock bug appeared in the previous build 1212.

Build 1212 (DLL ver. 10.0.1.10X )

  • Added support for SQL Server 2022.
  • Performance improvements for highly loaded servers.

Build 1203 (DLL ver. 9.7.7.1X )

  • Fixed dead-lock error in unlock_for_host.

Build 1201 (DLL ver. 9.7.3.2X )

  • Fixed "non-yielding scheduler" error that appeared on SQL Server 2016 from build 5820 and higher and SQL Server 2017 from build 3294 and higher.
  • Fixed errors for a database with enabled "Query Store".

Build 1197 (DLL ver. 9.6.5.2X )

  • Compatibility with SQL Server 2019 CU16.

Build 1196 (DLL ver. 9.6.4.2X )

  • Compatibility with SQL Server 2017 CU29.
  • Added warning when database size reaches 90% of the license limit.

Build 1195 (DLL ver. 9.6.3.1X )

  • Memory leak was fixed. This memory leak appeared in all versions of DbDefence.

Build 1194 (DLL ver. 9.5.21.0X )

  • Fixed database encryption API related to masking.
  • Fixed upgrade database issue for SQL Server 2019.

Build 1188 (DLL ver. 9.5.17.0X )

  • Support for SQL Server 2019 CU14.

Build 1186 (DLL ver. 9.5.16.0X )

  • Fixed bug with masked table and implicit CREATE STATISTICS.
  • Fixed bug in schema protection with excluded table when addressed as [database].[schema].[table].

Build 1184 (DLL ver. 9.5.10.0X )

  • Some queries to sysobjects table may display incorrect data.
  • Fixed issues with licenses on LOCALDB instances.

Build 1183 (DLL ver. 9.5.9.2X )

  • Fixes bug appeared in build 1171: some specific stored procedures cannot be created in an encrypted database.

Build 1182 (DLL ver. 9.5.9.1X )

  • Fixed issue with FILESTREAM data and imported key storage.
  • Fixed backup issue with FILESTREAM data on SQL Server 2019.

Build 1180 (DLL ver. 9.5.7.2X )

  • Fixed minor bug in GUI.

Build 1179 (DLL ver. 9.5.7.2X )

  • Fixed issue with deleting object and schema protection.
  • Fixed issue in masking functionality.

Build 1177 (DLL ver. 9.5.4.3X )

  • Fixed issues in masking functionality.

Build 1174 (DLL ver. 9.5.2.0X )

  • Fixed issues in masking functionality.

Build 1171 (DLL ver. 9.5.1.2X )

  • Potentially breaking change: when access declined by schema protection, SQL Server will raise Error 297 "The user does not have permission to perform this action.". Earlier was Error 208 "Invalid object name".
  • Fixed memory leaks in masking functionality.

Build 1166 (DLL ver. 9.5.0.2X )

  • Encryptor GUI can edit settings of an encrypted database.
  • Improved masking.

Build 1162 (DLL ver. 9.3.11.0X )

  • Compatibility with SQL Server 2019 CU10.

Build 1156 (DLL ver. 9.3.10.1X )

  • Fixed permission issues related to encryption with a certificates.

Build 1154 (DLL ver. 9.3.9.1X )

  • Fixed bug in the Encryptor GUI related to data masking validation. It could falsely report a validation error.

Build 1153 (DLL ver. 9.3.9.1X )

  • Compatibility with SQL Server 2019 CU9.

Build 1151 (DLL ver. 9.3.8.4X )

  • Fixed masking issues.
  • Improved performance for masked queries.
  • Adjusted permissions for database encryption. Now, it is only required to have ALTER ANY DATABASE permission. When using dbd_encrypt_db, it is enough to be the owner (db_owner).
  • More detailed error messages.

Build 1149 (DLL ver. 9.3.1.0X )

  • Fixed masking for HA cluster servers.
  • Attention: Breaking changes related ONLY to the databases encrypted with certificates: Backups produced by DbDefence v9.3.1.0 and higher can't be restored on an older version of DbDefence. Backups produced by an older version can be restored with the new version.
  • Fixed minor bug in 32-bit installer.

Build 1146 (DLL ver. 9.2.0.0X )

  • Masking for VIEWs.
  • Fixed bug in encryption API.

Build 1144 (DLL ver. 9.2.0.0X )

  • Minor changes in the installer.

Build 1142 (DLL ver. 9.2.0.0X )

  • To follow security regulations, DbDefence uses new FIPS-140 validated module #3503. Read more ...

Build 1130 (DLL ver. 9.0.12.8X )

  • Improved masking. Masks can be altered after encryption. Read more ...

Build 1113 (DLL ver. 9.0.8.4X )

  • Remote database encryption: dbd_encrypt_db.
  • DbDefence on Linux.
  • Improved backup performance.
  • Reduced locking. This improves overall performance on heavily loaded servers.

Build 1095 (DLL ver. 8.0.9.8X )

  • Compatibility with SQL Server 2016 SP2 CU13.

Build 1093

  • Finally fixed the bug in RESTORE LOG for some compressed backups.

Build 1092

  • Fixed unfixed bug in RESTORE LOG for some compressed backups.

Build 1090

  • Fixed bug in RESTORE LOG for some compressed backups.

Build 1089

  • Compatibility with SQL Server 2017 CU20.

Build 1088

  • Compatibility with SQL Server 2017 CU19.

Build 1086

  • Compatibility with SQL Server 2019 CU2.

Build 1084

  • No changes in the server module.
  • Improved compatibility with Microsoft Office 2019 and Client DLL.

Build 1083

  • Fixed non-exportable keys issue and FILESTREAM.
  • Fixed bug in the GUI.
  • Improved logging.

Build 1082

  • This build fixes performance degradation appeared in build 1046 (and above) on x64. It happened with enabled schema protection and when database was unlocked by frequent Open Symmetric Key statements.

Build 1081

  • Compatibility with SQL Server 2019 CU1.
  • Fix in API to prevent double encryption.

Build 1080

  • Database limit for the Free Version is set to 30 MB.

Build 1076

  • Support for SQL Server 2019.

Build 1058

  • Fixed bug in 64-bit dbdefence.dll appeared in June. Non DBO user couldn't unlock the database if schema protection was enabled.

Build 1057

  • Fixed minor bugs in Encryptor GUI

Build 1052

  • Fixed bug appeared in the previous release. Bug affects mostly SQL Server 2016 and 2017. Highly recommended to upgrade.

Build 1046

  • New feature: data masking.

What's new in DbDefence build 1023

  • New licensing options: 1 TB and 2 TB limits.
  • Improved performance on large servers.
  • Minor changes in Encryptor GUI.

What's new in DbDefence build 1021

  • Compatibility with Sophos AV Software.
  • Improved performance on large servers with many clients.
  • Binaries signed with High Assurance EV certificate from Digicert.

What's new in DbDefence build 1019

  • New 500,000 MB license.
  • Minor custom changes.

What's new in DbDefence build 1015

  • Compatibility with SQL Server 2014 SP3 (X86 and X64).
  • Security improvement in the command line encryptor. Now it reset the command line to hide sensitive data from Windows Task Manager.
  • Minor improvements in client dll.

What's new in DbDefence build 1010

  • SSL issues in DbDefence client DLL fixed.

What's new in DbDefence 7.4.1

  • Support for databases with memory optimized tables added.
  • Installer on SQL Server 2017 LOCALDB fixed.
  • Issues with activation on cluster fixed.

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

  • Issues with FILESTREAM with large number of files fixed.

What's new in DbDefence 7.3.10

  • Compatibility with SQL Server 2014 SP2 CU12 (X64) added.

What's new in DbDefence 7.3.3

  • A bug in backup system fixed: On average aproximately 0.5% of backups were corrupted (not critically). It is a good practice to verify backups with RESTORE VERIFYONLY command.
  • Compatibility with SQL Server 2012 build 11.0.7462.6 (X86) fixed.

What's new in DbDefence 7.3.1

  • Checks to encryption API added.
  • Function dbd_profiling to enable/disable profiling without re-encryption.
  • Compatibility with SQL Server 2017 CU4 (build 14.0.3022) fixed.

What's new in DbDefence 7.3

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

What's new in DbDefence 7.1

  • Support for SQL Server 2017 added.

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

  • Not-exportable keys added.
  • Options in Encryption API to allow access by login and non-exportable keys added.
  • Visual improvements in Encryptor GUI.

What's new in DbDefence 6.1

  • Support for SQL Server 2016 added.
  • Automatic access by login added.
  • Improved performance.
  • Several bugs fixed.

What's new in DbDefence 5

  • Support for SQL Server 2014 added.
  • Improved after-encryption tests.
  • Several bugs fixed.

What's new in DbDefence 4

The DbDefence 4 has several important improvements.

  • Client Program Configuration is completely rewritten. You do not need to specify passwords in the 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 DbDefence loads itself into the SQL Server process was also improved. It simplifies the distribution of encrypted data as a part of your installer.
  • The replication part was changed. If you used replication before, please check the documentation. You will need to setup passwords manually. Previous version of the software tried to do that automatically, but 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 the new version over the old one. Your activation key will work if you ordered it less than a year ago.