SSIS ADO.NET destination component in bulk insert mode disables foreign key CHECK Constraint - by BenAust

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 766249 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/5/2012 12:39:13 AM
Access Restriction Public


In a SSIS ppackage, when ADO.NET destination component is used in bulk insert mode it changes the CHECK constraint on foreign keys to NO CHECK on the destination table
Sign in to post a comment.
Posted by Microsoft on 4/1/2014 at 10:40 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SSIS. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available.

If the issue is a critical business interruption, please call CSS (Customer Support Services).

Thanks again for reporting the product issue and continued support in improving our product.

Mariusz Cichomski
Program Manager