Re my previous post on how not to be a sysadmin when comparing databases my joy has quickly been struck down by the above message!
Read more about Microsoft not acknowledging this to be a problem here Schema Compare permission error for Database Encryption Keys even though the type is set to be ignored
Blast! I can compare the schemas but not generate any script – even though cryptographic keys have nothing to do with it – because of this:
I’ve had success with the data compares, however, so a little progess was made after all.