Always encrypted is a new feature introduced to encrypt the in rest as well as during transport. It’s been quite long time the feature has been released to general public. In this encryption method the encryption will be done at the client side. Encryption keys can be stored in Azure vault, Windows certificate store in client server or in hardware module. Since the encryption keys doesn’t sit in the database engine it doesn’t reveal the actual data and even this is applicable for an administrators.
It’s been a month after the new year started. Hope everyone is having a wonderful time.
This is my first post for this year and it’s a simple one but most of them are looking around for this option quite from SQL Server 2012.
It’s been a week I was playing around this new feature. Now I’m going to drop\disable this feature so save some $ in my Azure subscription 🙂
I started testing the stretch tables quite some time and thought of blogging the experience.
In the last two days we saw whats stretch database and how to identify the tables. Today we will see how to stretch your database to Azure cloud. Before we start I would like mention it again that the tables you choose for streching will migrate all the data to Azure which means we can stretch only the archieve tables so dont just blindly add all the tables. Just include only the required archieve tables.