Home Dashboard Directory Help
Search

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


Status: 

Active


3
0
Sign in
to vote
Type: Bug
ID: 766249
Opened: 10/5/2012 12:39:13 AM
Access Restriction: Public
2
Workaround(s)
view
1
User(s) can reproduce this bug

Description

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

http://bennyaustin.wordpress.com/2012/10/04/ssis-ado-net-destination-in-bulk-insert-mode-and-foreign-keys/
Details
Sign in to post a comment.
Posted by Microsoft on 4/1/2014 at 10:40 PM
Hello
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
Microsoft
Sign in to post a workaround.
Posted by BenAust on 10/5/2012 at 12:40 AM
use OLEDB destination instead
Posted by BenAust on 10/5/2012 at 12:40 AM
Disable foreign keys before data loading and enable foreign keys after the data is loaded