I can't believe this still hasn't been done after more than a decade.

I have this issue. We store a Location Identifier as a column default constraint and do so in over 100 databases. The lack of a way to ignore default constraints makes SQL Compare difficult to use, since every table appears under "in both, but different" as a false positive. Make this happen, please!

Hello, this is 2021, its still not possible to ignore default constraints ?

Can't believe this still isn't an option - this was flagged up over 10 years ago!

Still a great improvement idea. Would make SQL Compare much more useful for comparing replicated dbs.
Right now, it's still quite a pain to filter out tables with just default constraints, and then manually filter the statements that I actually want to apply (indexes).

Have to compare ETL dbs to large source db with more than 11k tables. Don't care about defaults. Please add ignore option! I have to script out the schemas and then use a text comparison tool with REGEX. It would be great to be able to ignore defaults and constraints that don't exist in environments where they are not needed.

This would save so much time when deploying changes. Because defaults often change through the phases of Dev, Test, Live

This 'request' has been around for 10 years and has not been implemented.
Seriously? I would have thought that a) it would be a 101 option and b) very straight forward to implement.
See https://forum.red-gate.com/discussion/8816/ignore-default-statements

replicated tables at the subscriber is a good example. Should be able to ignore default constraints regardless of scenario. They are constraints like foreign keys, and there is currently an option to ignore foreign keys.