1

The 'clash' exception is happening updating NVARCHAR(MAX) using EF6 on an always encrypted field. Is this avoidable?

Tried changing the data type via latest SSMS and also getting 'clash' errors. Seems that now I have encrypted the columns I cannot alter the table at all either.

Sentinel
  • 3,582
  • 1
  • 30
  • 44
  • [This](https://blogs.msdn.microsoft.com/sqlsecurity/2015/08/27/using-always-encrypted-with-entity-framework-6/) may shed some light. – Nikhil Vartak Aug 13 '17 at 19:55
  • Unfortunately not – Sentinel Aug 13 '17 at 21:01
  • Could you please provide the complete error message that you are getting? – Nikhil Vithlani - Microsoft Aug 14 '17 at 17:38
  • I don't have it handy - basically if the field is nvarchar(max) and encrypted, you cannot save an update to it. Try to repro - I don't think I was doing anything special. It's the typical 'blah blah cannot save clash because of nvarchar not nvarchar(max) or something' error that always seems to happen with this always encrypted stuff – Sentinel Aug 14 '17 at 20:55

0 Answers0