Why do I keep losing connection in my SSIS package?

I have a very simple SSIS package where I take data from a view in Oracle, convert it minimally using the script component, and load it into a table in SQL Server 2008.

Both of my DB Source components and my DB components have successfully connected to their respective databases before.

Now I get the following error while debugging in BIDS (VS 2008).

Data flow task: ADO NET Destination failed to get connection {046C4CA9-2BBF-46FD-9FEA-06F1B173BB35}. The connection may have been damaged.

I installed the same with my Oracle connection, removing the connection component and creating a new one. The ADO.NET connection seems more stubborn. I made part of the username and password of my configuration for deployment. Is BIDS typical of this unstable environment? I need reliable connections so that I can fix other errors that I created. Thanks in advance for any help.

+4
source share
4 answers

Try using OLE DB for all connections if you do not have a specific need for ADO.NET ... you don’t know why, but it always seemed more reliable to me ...

+4
source

You might be better off if you just write your own download in C # or C ++ - you can spend a bit more time writing code, but you will spend much less time chasing elusive bugs and search errors for workarounds.

Edit: For those who stopped, could you please explain your reasons?

+2
source

In your DataFlow task, in the control flow view specified on the properties tab, the value for validating is true.

+1
source

set check delay = true in the properties window that worked for me

0
source

All Articles