Database Projects Schema Compare Ignore Extended Properties

Question

We use database project to deploy changes from the repo to the database. We created a schema compare to see what existing objects would be modified that we run before we update the database. We want it to ignore certain difference such as extended properties. However even with extended properties not checked in the compare options they still show. They are very confusing for none database folk because it says there is a difference but it doesn't show you want it is unless you expand the properties folder. More annoying though is the fact it doesn't actually script any changes so the same procedures and tables show up as being changed each compare, even if you push all the changes. Looking for some ideas if anyone else uses db projects and know if these can be excluded from a schema compare? Thanks so much!

Answer 1

Hi,

I used VS 2019 to create a new schema comparison. I used two databases with the same tables as the source and target.

When the extended properties not checked in the Schema compare options, the difference in Extended Properties on the objects in the two databases is indeed not detected.
Otherwise, it can be detected.