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.