Doesn't need to be user-defined. You can generate a query containing join criteria. Simply put a comma-separated list of table names into the Table Name field, and the join criteria into the WHERE field on the Selection tab. In the Columns grid make sure that no ambiguities exist by using fully-qualified column names in the Derivation field.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
If you are using Database stage then you can define INNER,RIGHT,LEFT, IN, NOT IN... manually in user-defined query...OCI consits of IN, NOT IN but RIGHT,LEFT outer join is not there...If you write user defined query you can tune query in your own way...
Or you can use the 'old' style outer syntax - (+) - in the generated sql which will get you everything but a full outer join. User defined sql is a... PITA... and should be avoided if at all possible. IMHO.
-craig
"You can never have too many knives" -- Logan Nine Fingers
You can use the database stage as reference link with where clause in select statement. Or if you want to do aggregations in the reference stage u need to use groupby and having clauses.
There you go. You've got a whole bunch of suggestions. But Rishabh, any reason why you would NOT want to use the hashed file for reference? Just curious.
</a>
