| title | Query columns using Always Encrypted with secure enclaves with SSMS | Microsoft Docs |
|---|---|
| ms.custom | |
| ms.date | 10/01/2019 |
| ms.reviewer | vanto |
| ms.prod | sql |
| ms.prod_service | database-engine, sql-database |
| ms.technology | security |
| ms.topic | conceptual |
| author | jaszymas |
| ms.author | jaszymas |
| monikerRange | >= sql-server-ver15 || = sqlallproducts-allversions |
[!INCLUDE tsql-appliesto-ssver15-xxxx-xxxx-xxx-winonly]
This articles describes how to use SQL Server Management Studio to issue queries that use a server-side secure enclave for Always Encrypted with secure enclaves, including:
- Queries that trigger in-place cryptographic operations - see Configure column encryption in-place with Transact-SQL
- Queries including range comparisons or pattern matching operations on columns encrypted with enclave-enabled keys.
To use SSMS to run queries on encrypted columns using a secure enclave, follow general instructions in Query columns using Always Encrypted with SQL Server Management Studio. Here are a few things that are specific to enclaves, you should be aware of:
- You need SSMS version 18.3 or higher.
- Make sure a query window, you are running queries utilizing a secure enclave from, uses a connection that has Always Encrypted and enclave computations enabled - see Enabling and disabling Always Encrypted for a database connection .