An error was received from SQL Server while attempting to reverse engineer elements of type Microsoft.Data.Schema.Sql.SchemaModel.ISql100DatabaseEncryptionKey

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.

Posted in SQL

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s