how clever is Dstage supposed to be?

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
SBSA_DW2
Premium Member
Premium Member
Posts: 37
Joined: Fri Jul 25, 2008 1:24 am

how clever is Dstage supposed to be?

Post by SBSA_DW2 »

Hi Guys

It's been a while. :D

I have records going into a transformer and then split either of two ways, one to LN_BSNS and the other to LN_PERSONAL. More often than not, there are no records going down to LN_PERSONAL which in turn does a inner JOIN to a fairly large Dataset.

My question is this - should Dstage recognize that no records are present and avoid a potentially costly JOIN operation?

thanks
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

No.

The join won't be costly. It relies on the fact that its inputs are sorted not to be costly. "End of data" appearing on LN_PERSONAL will mean that the Join stage gets to close without doing anything.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply