Are there any reasons an SSIS Lookup Transformation would give 0 output rows, neither matched or un-matched?

Question

I'm debugging an SSIS package locally in VS2019. I have an odd behavior where a lookup transform against a cache is receiving 22 rows on the input, but both the 'Match' and 'No Match' outputs are showing 0 rows. It does work sometimes, but only when data from an unrelated branch in the flow is not present. Are there reasons why a lookup would not include rows in either output? Or is this some kind of local execution bug?

Answer 1

what you mean by both the 'Match' and 'No Match' outputs are showing 0 rows?

Let's make a sample data and analyze the situation:

This is a Flat File Source data by branch:

Then connect this source data to LookUp Transformation.

Critical step is what to do with no-matching data (A good option is to send rows to no-match OLEDB Table)

On the connection Tab, Full-Cache Mode data corresponds to a table on a SQL Server DB

Join them by branch, and add manager to Pipeline:

Then send matched and non-matched records to 2 separate OLEDB destinations by designing tables in your local server:

End Result:

Now Lets check Match and Unmatched destination table :

Matched Records

Unmatched Records: