title: SSDT skips NOCHECK constraint in compares and publishes
body: <p>For some reason when using SSDT to either compare or modify a Table Foreign Key the software does not do anything to change the NOCHECK constraint set on the Foreign Key.</p>
  
  <p>This is the scripted setup for the table Foreign Key:</p>
  
  <h2>TABLE:</h2>
  
  <pre><code>ALTER TABLE [dbo].[SurveyQuestion]  WITH NOCHECK ADD  CONSTRAINT [FK_SurveyQuestion_Language] FOREIGN KEY([LanguageID])
  REFERENCES [dbo].[Language] ([ID])
  GO
  
  ALTER TABLE [dbo].[SurveyQuestion] CHECK CONSTRAINT [FK_SurveyQuestion_Language]
  </code></pre>
  
  <h2>DBSchema:</h2>
  
  <pre><code>CONSTRAINT [FK_SurveyQuestion_Language] FOREIGN KEY ([LanguageID]) REFERENCES [dbo].[Language] ([ID])
  </code></pre>
  
  <p>So, these are different settings, but SSDT just ignores them entirely.  Compares come back showing both are identical.</p>
  
  <p>In my publish profile I have "ignore with nocheck on check constraints" unchecked
  I also have "ignore withnocheck on foreign keys" unchecked.  So they both should be evaluated.</p>
  
  <p>Can anyone please try this out in a table of their own?  Just change your CHECK to NOCHECK in your database and run SSDT on it to see if SSDT fixes the discrepancy.</p>
  
  <p>I have tried and tried and SSDT keeps bypassing the discrepancy.</p>
  
  <p>Thanks</p>