| title | CREATE CRYPTOGRAPHIC PROVIDER (Transact-SQL) | Microsoft Docs | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| ms.custom | |||||||||
| ms.date | 03/14/2017 | ||||||||
| ms.prod | sql | ||||||||
| ms.prod_service | sql-database | ||||||||
| ms.service | |||||||||
| ms.component | t-sql|statements | ||||||||
| ms.reviewer | |||||||||
| ms.suite | sql | ||||||||
| ms.technology |
|
||||||||
| ms.tgt_pltfrm | |||||||||
| ms.topic | language-reference | ||||||||
| f1_keywords |
|
||||||||
| dev_langs |
|
||||||||
| helpviewer_keywords |
|
||||||||
| ms.assetid | 059a39a6-9d32-4d3f-965b-0a1ce75229c7 | ||||||||
| caps.latest.revision | 20 | ||||||||
| author | edmacauley | ||||||||
| ms.author | edmaca | ||||||||
| manager | craigg | ||||||||
| ms.workload | Inactive |
[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx-md]
Creates a cryptographic provider within [!INCLUDEssNoVersion] from an Extensible Key Management (EKM) provider.
Transact-SQL Syntax Conventions
CREATE CRYPTOGRAPHIC PROVIDER provider_name
FROM FILE = path_of_DLL
provider_name
Is the name of the Extensible Key Management provider.
path_of_DLL
Is the path of the .dll file that implements the [!INCLUDEssNoVersion] Extensible Key Management interface. When using the SQL Server Connector for Microsoft Azure Key Vault the default location is 'C:\Program Files\Microsoft SQL Server Connector for Microsoft Azure Key Vault\Microsoft.AzureKeyVaultService.EKM.dll'.
All keys created by a provider will reference the provider by its GUID. The GUID is retained across all versions of the DLL.
The DLL that implements SQLEKM interface must be digitally signed by using any certificate. [!INCLUDEssNoVersion] will verify the signature. This includes its certificate chain, which must have its root installed at the Trusted Root Cert Authorities location on a Windows system. If the signature is not verified correctly, the CREATE CRYPTOGRAPHIC PROVIDER statement will fail. For more information about certificates and certificate chains, see SQL Server Certificates and Asymmetric Keys.
When an EKM provider dll does not implement all of the necessary methods, CREATE CRYPTOGRAPHIC PROVIDER can return error 33085:
One or more methods cannot be found in cryptographic provider library '%.*ls'.
When the header file used to create the EKM provider dll is out of date, CREATE CRYPTOGRAPHIC PROVIDER can return error 33032:
SQL Crypto API version '%02d.%02d' implemented by provider is not supported. Supported version is '%02d.%02d'.
Requires CONTROL SERVER permission or membership in the sysadmin fixed server role.
The following example creates a cryptographic provider called SecurityProvider in [!INCLUDEssNoVersion] from a .dll file. The .dll file is named c:\SecurityProvider\SecurityProvider_v1.dll and it is installed on the server. The provider's certificate must first be installed on the server.
-- Install the provider
CREATE CRYPTOGRAPHIC PROVIDER SecurityProvider
FROM FILE = 'C:\SecurityProvider\SecurityProvider_v1.dll';
Extensible Key Management (EKM)
ALTER CRYPTOGRAPHIC PROVIDER (Transact-SQL)
DROP CRYPTOGRAPHIC PROVIDER (Transact-SQL)
CREATE SYMMETRIC KEY (Transact-SQL)
Extensible Key Management Using Azure Key Vault (SQL Server)