SQL Server 2016 Always Encrypted against existing database with multiple schemas doesn't work - by ThuanNguy

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.


1
0
Sign in
to vote
ID 3109591 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/28/2016 9:55:40 AM
Access Restriction Public

Description

SQL Server 2016 Always Encrypted against existing database with multiple schemas doesn't work as expected. When I want to encrypt a column of a schema, SQL Server SSMS and PowerShell tries to update other schemas which ends up with an error.
Sign in to post a comment.
Posted by Microsoft on 1/23/2017 at 8:54 PM
This issue was fixed in the recently released SSMS 16.5.2 (https://msdn.microsoft.com/en-us/library/mt238290.aspx)

Thanks,
-Matteo
Posted by Microsoft on 1/4/2017 at 5:26 PM
Thank you for reporting this bug. The fix for it will ship in the upcoming version of SSMS.