Release Notes - CDP for MSSQL 8.12.0
CipherTrust Database Protection for MSSQL (formerly known as ProtectDB for MSSQL) delivers powerful protection for the sensitive corporate and customer information stored in databases. With CDP, you have the flexibility to encrypt data at the column-level within databases, at the application layer, and during batch-driven data transformation and transaction processes.
This document may at times abbreviate CipherTrust Database Protection for MSSQL to CDP and CipherTrust Manager to Key Manager.
This release includes new feature, enhancements, and bug fixes. It also provides information on deprecated support.
Features and Enhancements
When CDP performs crypto operations in local mode, the error replacement values also get cached.
SafeNet protectDB for MSSQL has been rebranded to CipherTrust Database Protection for MSSQL.
SQL Server 2005 is no longer supported in CDP.
This section lists the fixed issues.
|PDB-3794||When you upgrade PDB versions (prior to 8.9.0) to 8.11.0, and you perform select operation, Null is displayed instead of an empty record.|
|PDB-3630||An AD group database user is not able to get the right access when its userPrincipalName is different from the samAccountName.|
CDP is compatible with:
CipherTrust Manager 2.4 or higher versions.
KeySecure Classic 8.12.3 or higher versions.
CDP can be upgraded from:
|Upgrade Path||Upgrade Path|
If you are upgrading from any versions prior to 8.9.0, first upgrade to PDB 8.9.0 and then upgrade to CDP 8.12.0.
Supported SQL Server Versions
CDP supports the following SQL Server versions:
|Supported Version||Supported Versions|
|SQL Server 2008||SQL Server 2012|
|SQL Server 2014||SQL Server 2016|
|SQL Server 2017||SQL Server 2019|