Page 1 of 1
Posted: Wed Apr 25, 2012 12:07 pm
by us1aslam1us
NOTFOUND works fine when performing lookup on Hashed Files but for the Table lookup it is always better to use the null check.
sAM
Posted: Wed Apr 25, 2012 12:24 pm
by chulett
Yes, always better because NOTFOUND doesn't really work for non-hashed file based lookups.
Hard to tell, though - is your lookup to a hashed file or directly to a database table?
Posted: Thu Apr 26, 2012 8:45 am
by Seyed
us1aslam1us wrote:NOTFOUND works fine when performing lookup on Hashed Files but for the Table lookup it is always better to use the null check.
sAM
Hi Sam,
Thank you for your input. You are correct. NOTFOUND would not work with database tables. To resolve this issue, my co-worker and I added an intermediate Hashed File stage and did a 'NOTFOUND' check on that. This worked and the row in question got loaded.
Thank you very much,
Seyed
Posted: Thu Apr 26, 2012 8:49 am
by Seyed
chulett wrote:Yes, always better because NOTFOUND doesn't really work for non-hashed file based lookups.
Hard to tell, though - is your lookup to a hashed file or directly to a database table?
Craig,
Thank you as always. To answer your quesiton, I was originally using NOTFOUND on ODBC stage. After adding an extra step by feeding the data from and ODBC stage to a Hashed File stage, the NOTFOUND worked and the row in question got loaded.
Thank you and continued success,
Seyed