SQL Compare - Why does the option 'Ignore Constraints' NOT ignore default constraint values?

Many of my databases have 1 column in every table with the same default value to identity which client owns that row when all the databases are replicated into 1 main database. Each time I try to compare 2 client databases, knowing the only difference should be the default constraint value in that one column, it will always show every table being different.
How can I tell SQL Compare to really IGNORE Default Constraint values?

Richard Wilcox April 19, 2022 17:23

Comments

1 comment

Hi @...
Thank you for reaching out on the Redgate forums.
I can confirm that at this time there is no option for ignoring default constraints. I do apologize for the inconvenience that this brings.

Looking at our Uservoice forum I believe you may have already raised a request for this - I may suggest voting on this one if it matches your request as it has more votes and more potential to be implemented into SQL Compare:
https://redgate.uservoice.com/forums/141379-sql-compare/suggestions/3463480-ignore-default-x-column-constraints

Jon_Kirkwood April 21, 2022 05:44

0

Add comment

Please sign in to leave a comment.

How can we help you today?

SQL Compare - Why does the option 'Ignore Constraints' NOT ignore default constraint values?

Comments

Add comment