RE: Optimizer Choices - Part Two - Light just came on...
From: Freeman Robert - IL <FREEMANR@xxxxxxxx>
To: "''oracle-l@xxxxxxxxxxxxx' '" <oracle-l@xxxxxxxxxxxxx>
Date: Fri, 1 Oct 2004 14:14:32 -0500
I should clarify that a bit though, the hash join appears to follow an
ORDERED hint and join the tables based on the FROM clause order if the
ORDERED hint is used. This is based on the 10053's that I generated.
RF
-----Original Message-----
From: Freeman Robert - IL
To: 'oracle-l@xxxxxxxxxxxxx'
Sent: 10/1/2004 2:12 PM
Subject: RE: Optimizer Choices - Part Two - Light just came on...
Wow.... it just hit me what a couple of you were trying to say to me
yesterday about the hash joins..... and I think that does answer my
question. Since by default the hash join will take the smaller table, no
mater what, it kind of limits the ability of the optimizer to choose the
better plan. Since dept was the smaller table, it will hash it first,
and thats what it's going to do, period.
Is that about the size of it?
Too many irons in the fire... the subconscious had to process what you
were trying to tell me.
Thanks for the feedback.
RF
--
http://www.freelists.org/webpage/oracle-l
