I have a data conversion which redirect truncated rows to a recordset.
What in reality I would like to achieve is to "fail the component" after
redirecting the rows. That is, I am insterested to know which rows are
causing the truncation, but when this happens, I would like to roll back
the package execution. I am achieving it through a script component
(using FireError), but it doesn't look that great solution.
Anyone has got a better idea?

--
ale
http://www.riolo.org

Alessandro Riolo wrote:
Another approach I am using "successfully" is to double the Data
Conversion transformations, that is, to redirect the Data Conversion
error output to another Data Conversion transformation, cloned from the
original one, but with fail component on truncation instead of redirect row.

--
ale
http://www.riolo.org

Hello Alessandro,


Put the data flow task in a Sequence container and make the sequence container
start a transaction.

What is you had a RowCount transform on the redirect path. In the control
flow after the Datapump you test the row count in an expression on the workflow.
This will lead to a Script task on the path that tests whether there were



Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Allan Mitchell wrote:
I failed to mention it was already in a Sequence container, anyway thank
nonetheless.

--
ale
http://www.riolo.org