Regarding Always Encrypted concept

Kartheek Vasantha 1 Reputation point
2020-08-14T05:57:04.76+00:00

Hi,
As everyone we are aware of the limitations on Always Encrypted concept like below.
a. Look for unsupported query patterns in ETL and identify alternatives.
eg:- 1. BULK INSERT INTO SELECT FROM TABLE.
2. Queries with filters like FirstName LIKE 'Bob%'
b. Passing above filter parameters into Stored procedures.
c. Does SSMS work with AzureKeyVault if we choose to use it for key storage or should it be stored locally?
and how do we register SSMS to access the key so we can write queries as usual.
d. Impact list for changing OLEDB to ADO.NET connection in our ETLs.

Any thoughts can helpful...

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,138 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. CathyJi-MSFT 21,111 Reputation points Microsoft Vendor
    2020-08-17T08:14:58.893+00:00

    Hi KartheekVasantha-5551,

    >how do we register SSMS to access the key so we can write queries as usual.

    Did you mean you want to Configure Always Encrypted by using Azure Key Vault? If I misunderstood, please let me know. Suggest you read this document Configure Always Encrypted by using Azure Key Vault to get more detail information about this.

    Best regards,
    Cathy

    0 comments No comments