What are the challenges you face when working across database platforms? Take the survey
Options

Schema Builds produced when the schema is not used

edited February 13, 2017 1:47PM in SQL Compare 11
Normally, one only needs a schema build script for a user when the schema is actually used. One can take the legitimate view that every database user should be mapped to an explicit schema. SQL Compare seems to tackle this in different ways under different circumstances. When comparing a database to a script, there are circumstances where SQL Compare wants to synchronize repeatedly in order to build these schemas yet they don't actually get into the script directory. It is giving me false positives of changes for which I have to delete the offending users to fix. I don't really want to exclude schemas from the comparison, even if I knew the command-line option to do it. Is there a better way?

Comments

Sign In or Register to comment.