NOCHECK Constraint in Compare but not in Source Control
ehuggz
Posts: 10 Bronze 1
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.
Is there a setting in Compare that will produce the same results as in Source Control?
ALTER TABLE [dbo].[CMS_CssStylesheetSite] WITHNOCHECK [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
Pinnacle of Indiana
Comments
Edit Project, Options, and select Ignore/With NOCHECK
Hope this helps.
(or you can equally change SQL Source Control to behave like SQL Compare)
Product Manager
Redgate Software
Thank you!
Pinnacle of Indiana