Thanks Raja.
Thanks Khurram.
Please validate my understanding for the other joins as well.
Merge Join : PI-PI join is on the same AMP. Hence no redistribution PI -Non PI join: Non PI column redistributed temporarily in spool. Non PI - NON PI join: Both are redistributed temporarily in spool. Small Table- Large Table : Samll table duplicated in spool and copied on all AMPS
HAsh join: Same as merge join case 4. but small table copied in the AMP memory.
Nested join: Happens on USI/PI column and when this column is equated to a constant.
so when optimizer comes across this scenario it will go for a nested join
is that right?
Thanks Raja.
Thanks Khurram.
Please validate my understanding for the other joins as well.
Merge Join : PI-PI join is on the same AMP. Hence no redistribution
PI -Non PI join: Non PI column redistributed temporarily in spool.
Non PI - NON PI join: Both are redistributed temporarily in spool.
Small Table- Large Table : Samll table duplicated in spool and copied on all AMPS
HAsh join: Same as merge join case 4. but small table copied in the AMP memory.
Nested join: Happens on USI/PI column and when this column is equated to a constant.
so when optimizer comes across this scenario it will go for a nested join
is that right?
Thanks for your help