NOCHECK Constraint in Compare but not in Source Control

ehuggzehuggz Posts: 10 Bronze 1
edited February 26, 2013 4:51PM in SQL Compare Previous Versions
I am using both Source Control and Schema Compare to manage migrations from Development to UAT. Source Control displays very few changes, while Compare shows a lot of changes to constraings with "NOCHECK" the only difference between the entries.
ALTER TABLE [dbo].[CMS_CssStylesheetSite] WITH
NOCHECK [code]ADD CONSTRAINT [FK_CMS_CssStylesheetSite_StylesheetID_CMS_CssStylesheet] FOREIGN KEY ([StylesheetID]) REFERENCES [dbo].[CMS_CssStylesheet] ([StylesheetID])

Is there a setting in Compare that will produce the same results as in Source Control?
Eric Huggins | Continuous Integration Manager
Pinnacle of Indiana


Sign In or Register to comment.