Home Dashboard Directory Help
Search

WITH CHECK | NOCHECK Warning on Foreign Keys in SSDT/Juneau by Markus Pöhler


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


2
0
Sign in
to vote
Type: Bug
ID: 760176
Opened: 8/29/2012 7:18:03 AM
Access Restriction: Public
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

Warnung nn SQL70588: Die WITH CHECK | NOCHECK-Option für die Erzwingung der Überprüfung vorhandener Daten wird ignoriert.
Details
Sign in to post a comment.
Posted by Neoafter on 12/3/2012 at 5:43 AM
Warning    159    SQL70588: WITH CHECK | NOCHECK option for existing data check enforcement is ignored.    

Warning is shown with the following code

ALTER TABLE [dbo].[D_Date] WITH CHECK ADD CONSTRAINT [FK_YSystem_Date] FOREIGN KEY([SystemKey])
REFERENCES [dbo].[D_Internal_System] ([SystemKey])

Posted by Microsoft on 9/27/2012 at 3:04 PM
We aren't able to reproduce this issue with the information provided. If you're still experiencing this issue, please pass on a repro script.

Thanks.
Posted by Markus Pöhler on 9/3/2012 at 9:01 AM
I have tried to add a video file several times but it failed. Today I got one uploaded after I have zipped it, but after the upload compledet, there is no file visible attached to this record.
Posted by Microsoft on 9/3/2012 at 1:32 AM
Thanks for your feedback. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 8/29/2012 at 11:25 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a video to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 8/29/2012 at 7:53 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.