I use Customer Id as my lookup key, set read type to TABLE and constrain the month using a WHERE clause ....
Instead of returning one row per Customer, I get as many rows as there are months eg if there are entries for a Customer for 6 months every input row generates 6 output rows
![Sad :(](./images/smilies/icon_sad.gif)
As an experiment I tried putting the Customer Id in the WHERE clause ie WHERE Customer_ID = 480397, expecting to get just 6 rows returned. Instead, I got exactly the same number of rows output as if there was no WHERE clause.
So it looks to me as if the DB2 EE plugin ignores the WHERE clause in a table read if the lookup type is Sparse.
Incidentally, I have tried User-Defined SQL as the Read Type for Sparse lookup and the job generally hangs ...
Anyone else got a 'conditional' Sparse lookup to work against DB2?