Skip to content

Commit a47eb0f

Browse files
authored
Merge pull request #33930 from Pietervanhove/patch-7
[PLEASE SQUASH] Update always-encrypted-wizard.md
2 parents ead93f0 + 5487f95 commit a47eb0f

File tree

1 file changed

+20
-3
lines changed

1 file changed

+20
-3
lines changed

docs/relational-databases/security/encryption/always-encrypted-wizard.md

Lines changed: 20 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: "Configure column encryption using Always Encrypted Wizard"
33
description: Learn how to set the Always Encrypted configuration for database columns by using the Always Encrypted Wizard in SQL Server.
4-
author: jaszymas
5-
ms.author: jaszymas
4+
author: Pietervanhove
5+
ms.author: pivanho
66
ms.reviewer: vanto
77
ms.date: "10/30/2019"
88
ms.service: sql
@@ -91,7 +91,24 @@ If you have configured a secure enclave in your database and you're using enclav
9191

9292
For more information about enclave attestation, see [Configure attestation for Always Encrypted using Azure Attestation](/azure/azure-sql/database/always-encrypted-enclaves-configure-attestation)
9393

94-
## Next steps
94+
## Post encryption
95+
96+
Clear the plan cache for all batches and stored procedures that access the table to refresh parameters encryption information.
97+
98+
```sql
99+
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE;
100+
```
101+
102+
> [!NOTE]
103+
> If you do not remove the plan for the impacted query from the cache, the first execution of the query after encryption might fail.
104+
>
105+
> Use `ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE` or `DBCC FREEPROCCACHE` to clear the plan cache carefully, as it can result in temporary query performance degradation. To minimize the negative impact of clearing the cache, you can selectively remove the plans for only the impacted queries.
106+
107+
Call [sp_refresh_parameter_encryption](../../system-stored-procedures/sp-refresh-parameter-encryption-transact-sql.md) to update the metadata for the parameters of each module (stored procedure, function, view, trigger) that are persisted in [sys.parameters](../..//system-catalog-views/sys-parameters-transact-sql.md) and might have been invalidated by encrypting the columns.
108+
109+
110+
## Related content
111+
95112
- [Query columns using Always Encrypted with SQL Server Management Studio](always-encrypted-query-columns-ssms.md)
96113
- [Run Transact-SQL statements using secure enclaves](always-encrypted-enclaves-query-columns.md)
97114
- [Develop applications using Always Encrypted](always-encrypted-client-development.md)

0 commit comments

Comments
 (0)