Re: Slow join performance
Posted by:
Ra Nala
Date: February 25, 2016 06:22AM
Rick James Wrote:
-------------------------------------------------------
> I'm still puzzled at the logic -- When
> "ea2.address_type = 'Bil'", you get the address
> fields displayed in the output. When it is !=
> 'Bil', you will get NULLs. This is not a typical
> way to do a WHERE clause. Usually you would want
> to skip the row completely. Please explain.
Sir, We need to all records from table : prdsl and want records if they matched from right table with condition ea2.address_type = 'Bil' if not just i want nulls from right table.
I dont want to miss records if not matches from right table that's why i wasn't included in where clause for the same condition.
> Perhaps the LEFT could (should) be removed from
> rn, be1, bea1, ea2 and make sure the indexes let
> the query start them them _before_ getting to the
> 4M-row psrl.
so your logic/approach applying is correct for tables: rn, be1, bea1, ea2 ?
yes indexes i need to check on what columns created exactly, this was i missed it.
Subject
Views
Written By
Posted
1867
November 27, 2015 04:55AM
1060
November 28, 2015 03:02PM
Re: Slow join performance
1016
February 25, 2016 06:22AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.