SQL 2016-Always Encrypted

As you know this has been introduced in sql server 2016, I am not going in details on it but would like to highlights some points which I learned today:

YOU WILL NEVER GET/READ THE REAL DATA FROM “SQL SERVER MANAGEMENT STUDIO”. IT WILL ALWAYS BEEN ENCRYPTED. THOSE COLUMNS HAS BE READ/WRITE USING APPLICATION CODE ONLY(having higher privilege)

  1. It intern uses self signed certificate for reading the data.
  2. Must required .NET FRAMEWORK 4.6
  3. Need to create COLUMN MASTER KEY and that has to be registered with COLUMN ENCRYPTION KEY.
  4. Presently Microsoft supports only 1 ALGORITHM as ‘AEAD_AES_256_CBC_HMAC_SHA_256’.
  5. Encryption type can be DETERMINISTIC support indexes,RANDOMIZED not supported/good for indexing.

Happy Learning.

 

ref:

https://msdn.microsoft.com/en-us/library/mt147923.aspx

limitations and errors related to always encryption:

T-SQL Tuesday #69 : Always Encrypted Limitations

 

 

 

Advertisements
This entry was posted in Limitation, sql 2016, What I learned today, Whats New and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s