October 2, 2015 at 1:47 pm
We are getting some data errors, and it seems to be coming from the SSIS package. I have traced it down, using a after update trigger, to the Data Flow Task that is reading in rows from a data source, and updating data in a different server's database. (by disabling the various Control Flow's)
The source does not have all the columns in its table, so the update is being passed the columns to update, Using OLE DB Source, lookup, and OLE DB Command. Looking at the Lookup Match Output's Metadata only the columns from the source table are there.
However when I run a trace I see "sp_execute" and every column in the table where I am writing the update to is showing up. I do not understand why... and how?
Of course the second question is why sometimes data in columns, not in the source, is being over written with data from a different row. The interesting part is that what is being mixed is rows with different document and item, the very thing that the lookup is keyed on. Plus it is in columns that are not in the source.
The OLE DB Command is using the following:
update zt_bor
set plant = ?
, Customer = ?
, Material = ?
, [SL No] = ?
,[Old RDD] = ?
,[New RDD] = ?
,[Order Qty] = ?
,[Prev Qty Confirmed] = ?
,[New Qty Confirmed] = ?
,[SU] = ?
,[DlBl] = ?
,[Created On] = ?
,[Old Load Date] = ?
,[New Load Date] = ?
,[MRP] = ?
,[Source Plant] = ?
,[CSR] = ?
,[TP Date] = ?
,[Stocking_Strategy] = ?
where Document = ? and Item = ?
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply