NOCHECK Constraint in Compare but not in Source Control

Compares and synchronizes SQL Server databases, backups and scripts.

Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong

NOCHECK Constraint in Compare but not in Source Control

Postby ehuggz » Tue Feb 26, 2013 8:22 pm

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.

Code: Select all
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
ehuggz
 
Posts: 7
Joined: Tue Aug 14, 2012 9:41 pm
Location: South Bend, IN

Postby David Atkinson » Tue Feb 26, 2013 9:31 pm

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
 
Posts: 1124
Joined: Mon Dec 05, 2005 4:54 pm
Location: Twitter: @dtabase

Thank you

Postby ehuggz » Tue Feb 26, 2013 10:51 pm

Saved me a lot of digging, even if it should be obvious.
Thank you!
Eric Huggins | Continuous Integration Manager
Pinnacle of Indiana
ehuggz
 
Posts: 7
Joined: Tue Aug 14, 2012 9:41 pm
Location: South Bend, IN


Return to SQL Compare 10

Who is online

Users browsing this forum: Yahoo [Bot] and 1 guest