Results 1 to 3 of 3
  1. #1

    Default SQL Server 2016's Always Encrypted Feature


    I read about the Always Encrypted feature of SQL Server 2016 but does it really solve the problem when your data isn't in relational database?

  2. #2


    If you are using the direct access model, say a WPF application that talks to the database, the username and password won't be enough. For decrypting values you will require the certificate.
    Decryption is easily possible only when you are using the middle three tier model.

    But the Always Encrypted feature will reduce the damage caused by hacking of your database backups.

  3. #3
    Join Date
    Apr 2015


    Quite sure you get a username and a password to get access to the database. The data is usually encrypted at the application level. It doesn't solve the problem though as sometimes your data is not in relational db.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts