title: SQL Always Encrypted vs SQL Dynamic Data Masking
body: <p>I am undecided on two methods to hide data in a single column in SQL Server DB.</p>
  <p><code>1. SQL Always Encrypted</code></p>
  <p><code>2. SQL Dynamic Data Masking</code></p>
  <p>After reading articles for both, my understanding is that <code>Always Encrypted</code> may be more secure than <code>Dynamic Data Masking</code> as the data stored is encrypted instead of the putting a mask on top of the password.</p>
  <p>However, what are the impacts when it comes to daily usage in this scenario if the user simply wants to hide the password field from database administrators?</p>
  <blockquote>
  <p>Data to be hidden: Password</p>
  <p>Functions using Password column: Reset password, change password, insert new password row when creating new user</p>
  </blockquote>
  <p>Any advice would be appreciated.</p>
  <hr />
  <p><em>P.S. My initial plan was to use SHA1+Salt hashing to password fields and storing hash values instead of password. However, if the requirements are simply to hide the field in DB, I find that the other 2 methods above may be sufficient.</em></p>