Retaining And Using Same DB Connection For Whole Package

Hello,
I need some help to solve an issue we have with SSIS, perhaps someone could help us.

We need to extract data from a remote database. We would like to use SSIS to extract data from that DB. But our actions are very restricted in that DB; we can query the DB views and create (local, global) temp tables only.

So, we created an SSIS package with two SQL execution tasks. In the first task, we create two local temp tables and insert some results into them. In our second task, we need to access the values stored into the temp tables, so we have the two tasks connected and we set the RetainSameConnection to true.

But when we execute, the second task always fails reporting €œinvalid object name€? (referring to the temp table names). It looks like each task is using a different DB, making impossible for us to use the temp tables we created in the first task. We tried both ADO.net and OLEDB without much luck so far.

Any ideas how to solve this problem? Any hints and recommendations are much appreciated.

As a side note, we are trying to avoid global tables because our test team will need to test our code and if the code is run by both SSIS and our test team at the same time, then we€™ll have problems. Unless we synchronize access to the tables, or pass some sort of caller identifier to prefix or suffix each temp table name with that caller identifier. No option looks very elegant so far, but anyway.

So, do you know if just one database connection could be used for the whole flow (or not)? And if yes, how?

Thanks and regards,
Claudio