Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Tasks

Using Separate Properties Files for Different SQL Database Instances

search

Using Separate Properties Files for Different SQL Database Instances

This section provides information on using separate properties files for different SQL database instances.

Note

Before performing this step, ensure all the properties file must have similar file permissions.

Each SQL database instance can use its own properties file, allowing you to configure parameters independently according to the requirement.

To use this with the CAKM for Microsoft SQL Server EKM Provider, navigate to the installation directory of the provider and copy the cakm_mssql_ekm.dll, and cakm_mssql_ekm.properties files to the desired location.

Now, load the cryptographic provider from this new location using the following query:

CREATE CRYPTOGRAPHIC PROVIDER <provider_name> FROM FILE ='<new_location>'

Example:

Consider you have two SQL database instances on the same machine — one running SQL Server 2016 and another running SQL Server 2019.

  • On SQL Server 2016, where cakm_mssql_ekm.dll and cakm_mssql_ekm.properties files are located in the default path C:\Program Files\CipherTrust\CAKM.

To load the cryptographic provider, execute the following query:

CREATE CRYPTOGRAPHIC PROVIDER <provider_name> FROM FILE ='C:\Program Files\CipherTrust\CAKM For SQLServerEKM\cakm_mssql_ekm.dll'
  • On SQL Server 2019, create a desired folder, say MSSQL2019. Copy cakm_mssql_ekm.dll and cakm_mssql_ekm.properties files from SQL Server 2016 and place them inside MSSQL2019.

Now, load the cryptographic provider from this new location using the following query:

CREATE CRYPTOGRAPHIC PROVIDER <provider_name> FROM FILE ='C:\Program Files\CipherTrust\CAKM For SQLServerEKM\MSSQL2019\cakm_mssql_ekm.dll'

Hence, both the instances are using separate properties file located in different paths.

Note

  • When copying the properties file, it is recommended to provide a unique Log File path in each properties file for every SQL database instance. This will avoid any discrepancies in the Log File.

  • The cakm_mssql_ekm.properties file must be placed in the same folder where provider DLL is copied. For one instance of database server only one library and property file can be used.

For more information on how to configure, refer to Configuring Properties File.

On this page