Skip to content

Latest commit

 

History

History
69 lines (54 loc) · 2.56 KB

File metadata and controls

69 lines (54 loc) · 2.56 KB
title DROP CRYPTOGRAPHIC PROVIDER (Transact-SQL) | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql
ms.prod_service sql-database
ms.reviewer
ms.technology t-sql
ms.topic language-reference
f1_keywords
DROP CRYPTOGRAPHIC PROVIDER
DROP_CRYPTOGRAPHIC_PROVIDER_TSQL
dev_langs
TSQL
helpviewer_keywords
DROP CRYPTOGRAPHIC PROVIDER statement
ms.assetid 71c55c20-439e-4897-aef5-f20e556d668f
author VanMSFT
ms.author vanto

DROP CRYPTOGRAPHIC PROVIDER (Transact-SQL)

[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx-md]

Drops a cryptographic provider within [!INCLUDEssNoVersion].

Topic link icon Transact-SQL Syntax Conventions

Syntax

  
DROP CRYPTOGRAPHIC PROVIDER provider_name   

Arguments

provider_name
Is the name of the Extensible Key Management provider.

Remarks

To delete an Extensible Key Management (EKM) provider, all sessions that use the provider must be stopped.

An EKM provider can only be dropped if there are no credentials mapped to it.

If there are keys mapped to an EKM provider when it is dropped the GUIDs for the keys remain stored in [!INCLUDEssNoVersion]. If a provider is created later with the same key GUIDs, the keys will be reused.

Permissions

Requires CONTROL permission on the symmetric key.

Examples

The following example drops a cryptographic provider called SecurityProvider.

/* First, disable provider to perform the upgrade.  
This will terminate all open cryptographic sessions. */  
ALTER CRYPTOGRAPHIC PROVIDER SecurityProvider   
SET ENABLED = OFF;  
GO  
/* Drop the provider. */  
DROP CRYPTOGRAPHIC PROVIDER SecurityProvider;  
GO  

See Also

Extensible Key Management (EKM)
CREATE CRYPTOGRAPHIC PROVIDER (Transact-SQL)
ALTER CRYPTOGRAPHIC PROVIDER (Transact-SQL)
CREATE SYMMETRIC KEY (Transact-SQL)