Re: hash join and nested loop join in an oltp query

  • From: Mladen Gogala <mladen@xxxxxxxxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Tue, 4 May 2004 15:04:28 -0400

On 05/04/2004 02:43:13 PM, ryan.gaffuri@xxxxxxx wrote:
>
> what types of cases make hash joins superior to nested loops? I see them alot 
> in batch processing when I need > to  join most of the rows, but I am see 
> them now when I return a small subset of rows.

Well, if you have to use full table scan to retrieve rows from one of the 
tables,
there is a strong probability that hash join will be faster then the nested loop
approach. Of course, there is a slight problem with the word OLTP, because full
table scans are not allowed in OLTP queries.

> has anyone experienced this? 

Probably.
-- 
Mladen Gogala
Oracle DBA



Note:
This message is for the named person's use only.  It may contain confidential, 
proprietary or legally privileged information.  No confidentiality or privilege 
is waived or lost by any mistransmission.  If you receive this message in 
error, please immediately delete it and all copies of it from your system, 
destroy any hard copies of it and notify the sender.  You must not, directly or 
indirectly, use, disclose, distribute, print, or copy any part of this message 
if you are not the intended recipient. Wang Trading LLC and any of its 
subsidiaries each reserve the right to monitor all e-mail communications 
through its networks.
Any views expressed in this message are those of the individual sender, except 
where the message states otherwise and the sender is authorized to state them 
to be the views of any such entity.

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: