Interesting Data Flow task Problem

hi i have an issue in Dataflow task basically i have 10 or more Dataflow tasks in a package and i intend to do is capture the Input FileName and Destination Name of that DataFlow Task into a Sql server Table.

I donot want to hard code but is there a way of storing these names in variables or getting the name from dts runtime properties to store them into a table.

My purpose to capture these values is to log these values along with error rows into a table.

A data flow can have more than one input/output. In fact, a data flow doesn't even have to have an input or an output that is external to the flow. (You can have a script source... You can omit a destination entirely because maybe you just need to execute an OLE DB Command transformation for every row...)

I'm not entirely clear on your question/problem... How does each data flow (of the 10 or more) know what source and destinations to use? Isn't that hardcoded?|||

the connection managers for the source and destination are dynamic from configuration table in sql server and what i am trying to do is in case of error log the source filename , destination table name with error row and description into a error table.

i am confused about how to get the actual file name and destination table name , in my case i use seperate DFT dataflow task for each separate table to load.

|||

Dev2624 wrote:

the connection managers for the source and destination are dynamic from configuration table in sql server and what i am trying to do is in case of error log the source filename , destination table name with error row and description into a error table.

i am confused about how to get the actual file name and destination table name , in my case i use seperate DFT dataflow task for each separate table to load.

Are you assigning the source and destination to the ConnectionString parameters, or are you assigning them to a variable?

You can hook the configuration table connectionstring parameters up to package variables, and then use the variables in the connection manager's expression property for ConnectionString. Then, since the configuration is in a variable, simply copy the variable's value to your logging output. Basically.