Foreign keys recreated with NOCHECK during data sync
We have the same issue as noted here: http://www.red-gate.com/messageboard/viewtopic.php?t=13662&highlight=foriegn+foreign+key
The FK is recreated with NOCHECK during data sync which triggers a schema change.
Mark Snelling commented
Any movement on this?
Definately feels like a bug when changes "magically" appear in the schema
This is causing us some issues too. It's a shame that the software provides the ability to do this but doesn't give you full control of how it will do it or how you want it to do it and so we have a trigger for a schema change.
Franz Junge commented
Yup, this is a bit rubbish.