Hi Albert,

I've used a prior version of encryption in development -- that was a real pain. I haven't used this one, as we haven't had the need.

This method is the easiest there is to use, hands down. It is also considered the safest. No matter what kind of security method you use, there will always be a need to get the encryption key to where it is being used. The rules for that are rather detailed. Search on KMS (Key Management System) and be prepared for glazed-eyes phenomenon, until the picture comes clear.

Hank

>Thanks Hank. Have you used this option or any other encrypting options in SQL Server? Just wondering what your experience was like.
>
>Albert
>
>>HI Albert,
>>
>>The "Always Encrypted" option in SQL Server is the best way to go: https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-ver15 It is seamless, data is encrypted at rest and on the network.
>>
>>Hank
>>
>>>Hi all,
>>>
>>>Forgive me...tired today and just need to think out loud. New company is going to take over and redevelop the app I have done for a client and move it into MSFT Dynamics (or at least that is the plan - we'll see if they can get it to do what the VFP app did).
>>>
>>>We have talked about data encryption. This company has a lot of sensitive data (PII, banking, payments data etc.) which we handled in VFP by doing field level (column level) encryption. So now I am talking to them about what they are proposing for encryption.
>>>
>>>Not knowing SQL (which is what I assume is behind Dynamics), I am flying a bit blind here in my discussions.
>>>
>>>They are suggesting "file level encryption" at the database level. They are not really clear - I think they are suggesting encrypting the entire database in SQL. We did the column level encryption because even if this company had a data breach and scooped up all the VFP tables, they would still not be able to read the columns with sensitive information.
>>>
>>>How have others encrypted data - pros and cons and what scenarios were you trying to protect against?
>>>
>>>Thanks,
>>>Albert