Limitations

User Specified Error Replacement Value For Large Object

For users without sufficient permissions to access the migrated data, CDP for MSSQL can be configured to return any of the following:

• Standard "insufficient permissions" error

• NULL value (not the error)

Group Mapping or Role Mapping

The Group Mapping or Role Mapping feature works only on the database roles. The feature does not work for the UDFs such as ing_gn_rndm, where the database name (required for mapping) is not passed.

Large Objects

In CDP for MSSQL, large objects up to 500MB are supported. This size may be less depending upon the heap size available on the CipherTrust Manager.

Name UDFs

Name UDF (for example, ing_e_chr_nm420) operations are not permitted while online migration/key rotation is in progress.

User Specified Error Replacement Value is Not Supported for Float Data Type

The user specified error replacement value is not supported for Float data types. Standard error and Null value replacement are supported.

Unable to Set Column Properties for the Float(n) Data Type, Where n<=24

The connector does not allow setting the properties for a column of the float(n) data type, where n<=24. This data type internally gets converted into the real data type by the SQL Server. The real data type is not supported in the CDP for MSSQL.

Large Object Data Size Limitation

For large objects, the maximum data size supported for cryptographic operations is 15-20% of the maximum CLR memory available to SQL Server.

The Error Replacement feature is not supported for some of the data types if:

• The data length exceeds 1022 bytes for CHAR and 512 bytes for NCHAR.

• The data length exceeds 3072 bytes for VARCHAR and 1536 bytes for NVARCHAR.