Add option to drop a constraint instead of a "nocheck"
My suggestion is to have an option to drop a foreign key in data compare instead of doing a "NOCHECK" / "WITH CHECK CHECK CONSTRAINT" with an "ALTER TABLE". Yes the way its done covers most cases but sometime the foreign key name need to be renamed in the same time. A drop/create can solve the issue. It's just a way to provide more control.
1
vote
![](https://secure.gravatar.com/avatar/f8d7bf5beb1706a982cafa15568c3c18?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)