"Okay, I accept that distinction... it is an SQL destination with that limitation; not an OLE-DB destination.  But, "Destinations" from that portion of the toolbox do not have success outputs, so another task after a destination isn't possible (except perhaps by either passing a result set to a new control flow, or implementing an event handler).  It is not possible within the data flow after the destination task."

Right, but you can split the flow with a multicast before the destination.

"Yes, an SQL Script component could have been used..."

What I meant was with a SQL Script in the SQL Task or multicast into a separate flow where you could do the updates. I don't know what it is you're attempting to update, so I'm just visualizing. You might be able to mark the rows flowing into the destination with a flag and then do set based post-processing with the SQL task for whatever updates you were planning in the OLEDB Command Destination. Or, flow into a temporary table, do the processing there and then update the destination table with the staged data. Maybe this approach will be more performant than the row by row commands you're doing as well.

Thanks,

K