Redaguoti

Bendrinti naudojant

Configure column encryption in-place with Transact-SQL

  • Straipsnis

Applies to: SQL Server 2019 (15.x) and later - Windows only Azure SQL Database

This article describes how to perform cryptographic operations in-place on columns using Always Encrypted with secure enclaves with the ALTER TABLE Statement/ALTER COLUMN statement. For basic information about in-place encryption and general pre-requisites, see Configure column encryption in-place using Always Encrypted with secure enclaves.

With the ALTER TABLE or ALTER COLUMN statement, you can set the target encryption configuration for a column. When you execute the statement, the server-side secure enclave will encrypt, re-encrypt, or decrypt the data stored in the column, depending on the current and the target encryption configuration specified in the column definition in the statement.

  • If the column is currently not encrypted, it will be encrypted if you specify the ENCRYPTED WITH clause in the column definition.
  • If the column is currently encrypted, it will be decrypted (converted to a plaintext column), if you don't specify the ENCRYPTED WITH clause in the column definition.
  • If the column is currently encrypted, it will be re-encrypted if you specify the ENCRYPTED WITH clause and the specified column encryption type or the column encryption key are different from the currently used encryption type or the column encryption key.

Note

You cannot combine cryptographic operations with other changes in a single ALTER TABLE/ALTER COLUMN statement, except changing the column to NULL or NOT NULL, or changing a collation. For example, you cannot encrypt a column AND change a data type of the column in a single ALTER TABLE/ALTER COLUMN Transact-SQL statement. Use two separate statements.

As any query that uses a server-side secure enclave, an ALTER TABLE/ALTER COLUMN statement that triggers in-place encryption must be sent over a connection with Always Encrypted and enclave computations enabled.

The remainder of this article describes how to trigger in-place encryption using the ALTER TABLE/ALTER COLUMN statement from SQL Server Management Studio. Alternatively, you can issue ALTER TABLE/ALTER COLUMN from Azure Data Studio or your application.

Note

Currently, the Invoke-Sqlcmd cmdlet in the SqlServer PowerShell module and sqlcmd, do not support using ALTER TABLE/ALTER COLUMN for in-place cryptographic operations.

Perform in-place encryption with Transact-SQL in SSMS

Pre-requisites

Steps

  1. Open a query window with Always Encrypted and enclave computations enabled in the database connection. For details, see Enabling and disabling Always Encrypted for a database connection.

  2. In the query window, issue the ALTER TABLE/ALTER COLUMN statement, specifying the target encryption configuration for a column you want to encrypt, decrypt or re-encrypt. If you're encrypting or re-encrypting the column, use the ENCRYPTED WITH clause. If your column is a string column (for example, char, varchar, nchar, nvarchar), you may also need to change the collation to a BIN2 collation.

    Note

    If your column master key is stored in Azure Key Vault, you might be prompted to sign in to Azure.

  3. Clear the plan cache for all batches and stored procedures that access the table, to refresh parameters encryption information.

    ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE;

    Note

    If you do not remove the plan for the impacted query from the cache, the first execution of the query after encryption may fail.

    Use ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE or DBCC FREEPROCCACHE to clear the plan cache carefully, as it may result in temporary query performance degradation. To minimize the negative impact of clearing the cache, you can selectively remove the plans for the impacted queries only.

  4. Call sp_refresh_parameter_encryption to update the metadata for the parameters of each module (stored procedure, function, view, trigger) that are persisted in sys.parameters and may have been invalidated by encrypting the columns.

Examples

Encrypting a column in-place

The below example assumes:

  • CEK1 is an enclave-enabled column encryption key.
  • The SSN column is plaintext and is currently using the default database collation, such as Latin1, non-BIN2 collation (for example, Latin1_General_CI_AI_KS_WS).

The statement encrypts the SSN column using deterministic encryption and the enclave-enabled column encryption key in-place. It also overwrites the default database collation with the corresponding (in the same code page) BIN2 collation.

The operation is performed online (ONLINE = ON). Also note the call to ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE, which recreates the plans of the queries is affected by the table schema change.

ALTER TABLE [dbo].[Employees]
ALTER COLUMN [SSN] [char](11) COLLATE Latin1_General_BIN2
ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = [CEK1], ENCRYPTION_TYPE = Deterministic, ALGORITHM = 'AEAD_AES_256_CBC_HMAC_SHA_256') NOT NULL
WITH
(ONLINE = ON);
GO
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE;
GO

Re-encrypt a column in-place to change encryption type

The below example assumes:

  • The SSN column is encrypted using deterministic encryption and an enclave-enabled column encryption key, CEK1.
  • The current collation, set at the column level, is Latin1_General_BIN2.

The below statement re-encrypts the column using randomized encryption and the same key (CEK1)

ALTER TABLE [dbo].[Employees]
ALTER COLUMN [SSN] [char](11) COLLATE Latin1_General_BIN2
ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = [CEK1]
, ENCRYPTION_TYPE = Randomized
, ALGORITHM = 'AEAD_AES_256_CBC_HMAC_SHA_256') NOT NULL;
GO
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE;
GO

Re-encrypt a column in-place to rotate a column encryption key

The below example assumes:

  • The SSN column is encrypted using randomized encryption and an enclave-enabled column encryption key, CEK1.
  • CEK2 is an enclave-enabled column encryption key (different from CEK1).
  • The current collation, set at the column level, is Latin1_General_BIN2.

The below statement re-encrypts the column with CEK2.

ALTER TABLE [dbo].[Employees]
ALTER COLUMN [SSN] [char](11) COLLATE Latin1_General_BIN2
ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = [CEK2]
, ENCRYPTION_TYPE = Randomized
, ALGORITHM = 'AEAD_AES_256_CBC_HMAC_SHA_256') NOT NULL;
GO
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE;
GO

Decrypt a column in-place

The below example assumes:

  • The SSN column is encrypted using an enclave-enabled column encryption key.
  • The current collation, set at the column level, is Latin1_General_BIN2.

The below statement decrypts the column and keeps the collation unchanged. Alternatively, you can choose to change the collation. For example, change the collation to a non-BIN2 collation in the same statement.

ALTER TABLE [dbo].[Employees]
ALTER COLUMN [SSN] [char](11) COLLATE Latin1_General_BIN2
WITH (ONLINE = ON);
GO
ALTER DATABASE SCOPED CONFIGURATION CLEAR PROCEDURE_CACHE;
GO

Next steps

See also