Setting up Always Encrypted on an existing table fails with errors on unrelated objects - by Kenneth Fisher

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 3103181 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/15/2016 8:23:07 PM
Access Restriction Public


Using either the wizard or PoSH to encrypt a column on an existing table appears to run a check on all objects in the database and return an error if there are any problems even on unrelated objects.  I've been unable to encrypt a column with errors in views, stored procedures and check constraints.
Sign in to post a comment.
Posted by Microsoft on 1/23/2017 at 8:55 PM
This issue was fixed in the recently released SSMS 16.5.2 (

Posted by Microsoft on 1/4/2017 at 5:31 PM
Thank you for reporting this bug. It has been fix and the fix will ship in the next refresh of SSMS.