How can we help you today? How can we help you today?

NOCHECK Constraint in Compare but not in Source Control

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?
ehuggz
0

Comments

2 comments

  • David Atkinson
    Try:

    Edit Project, Options, and select Ignore/With NOCHECK

    Hope this helps.

    (or you can equally change SQL Source Control to behave like SQL Compare)
    David Atkinson
    0
  • ehuggz
    Saved me a lot of digging, even if it should be obvious.
    Thank you!
    ehuggz
    0

Add comment

Please sign in to leave a comment.