I was wondering if there was a way to further examine a redirected rows
from a lookup?

For Example:

If I have a lookup comaring two sources (Flat File against a DB Table)
and redirecting rows that do not match---Can I perform a transform that
will detect the columns and values that did not match?

I would like to store the columns of the unmatched values into a
variables and use it in a OLE DB statement.

The idea would be that I map the variables to a parameters so that I
wouldn't have to write arduous SQL statements for large tables in our
Data Repository.

For Example: (I don't want to have to write an OLE DB like this):

UPDATE <table>
SET <column1> = ?, <column2> = ?, <column3> = ?, <column4> =
?,....<column55> = ?

It would be nice to write it like this:

UPDATE <table>
SET ?* = ?**

?* = the columns identified in the lookup
?** = the values identified in the lookup

================================================== =================

I might be thinking about this whole process wrong, so any information
that might point me in the right direction would be appreciated

Hello Travis,

The rows you pipe to the error output can be used however you want. They
can essentially become another source to the pipeline. Using the OLE DB
transform then you would have to issue a statement

UPDATE <table> SET <col> = ?, <col2> = ? etc

you then map the incoming columns from the error output to the right ?

If you do not like this (row based) then stage these rows and outside of
the data flow issue a set based UPDATE in an ExecuteSQL task.



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