Comments
Sort by recent activity
This is only an issue if you have it combined with static data and you have option "check for changes to static data" enabled. Which I guess, makes sense if one of the static checked tables has an encrypted column because you cannot share static data with SQL Server encrypted values between developers with different certificates/keys. If there is a work around this would most likely be insecure due to the data/scripts having secure data in plaintext. Am I on the right track here? Best guess, you should not have any tables with encrypted data selected as static data. [image] / comments
This is only an issue if you have it combined with static data and you have option "check for changes to static data" enabled. Which I guess, makes sense if one of the static checked tables has an ...