[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 617
  • Last Modified:

oracle: better the perfomrnace. inner join vs partition by

I have 2 querys, the former takes more than 15 minutes.
query 1
select      
          ts1.CodUnico,
            ts1.RazonSocial,
            ...
            ts1.LineaCredTienda
from        tmp_Solicitud ts1 inner join tmp_Solicitud ts2
            on ts1.CODSOLICITUD = ts2.CODSOLICITUD
            and ts2.codsolicitud = (select max(t.codsolicitud)
                                    from tmp_Solicitud t  
                                    where ts2.CodUnico = t.CodUnico);  
                                   

query 2
SELECT
       codunico,
       razonsocial,
       numerodocumento,
       codtipobanca,
       codgrupo,
       codcalificacionsbs,
       codfeve,
       rating,
       codsegmentacion,
       codejecutivonegocios,
       desejecutivonegocios,
       lineacredtienda
  FROM (SELECT codunico,
               razonsocial,
               numerodocumento,
               CASE codtipobanca
                   WHEN 1 THEN 'Corporativa BC'
                   WHEN 2 THEN 'Empresa BE'
                   WHEN 3 THEN 'Institucional BI'
                   WHEN 4 THEN 'Leasing LS'
               END
                   codtipobanca,
               codgrupo,
               codcalificacionsbs,
               codfeve,
               rating,
               CASE codsegmentacion WHEN '1' THEN '1' ELSE '0' END codsegmentacion,
               codejecutivonegocios,
               desejecutivonegocios,
               lineacredtienda,
               RANK() OVER (PARTITION BY codunico ORDER BY codsolicitud DESC) r
          FROM tmp_solicitud)
 WHERE r = 1

Thanks to you, the query was modified and now takes less than 2 seconds, my question is why?
 Deputy respective execution plans.
 Greetings

partitionBY.jpg
INNERjoin.jpg
0
enrique_aeo
Asked:
enrique_aeo
  • 3
  • 2
3 Solutions
 
sdstuberCommented:
The first queries the same table 3 times including extra work for aggregation and filtering on the aggregate

The second queries the table only once and then sorts the data.

The first does a lot more work, hence more time
0
 
sdstuberCommented:
The

select .... from (select....)

might make it appear there are two queries needing double io, but there isn't.  The inner query is called an inline view and is merely a logical construction for syntax.  Looking at the plan you can see there is only one IO  (TABLE ACCESS FULL) which makes sense since the table is only referenced once in the query (the FROM clause)

the other query clearly  references the table 3 times, so regardless of any syntax constructions the query will hit the table 3 times once for each reference and the plan shows that
0
 
slightwv (䄆 Netminder) Commented:
Since your question has to do with performance:  What version of Oracle are you using?

I noticed you are using Rule-Based Optimization.  If possible and you aren't using it 'by choice', I would look into using Cost-Based Optimization.

Check the online documentation for your version.

Here's the 11Gr2 link (It's what I have bookmarked):
http://download.oracle.com/docs/cd/E11882_01/server.112/e17120/ds_appdev004.htm#ADMIN12198
0
 
sdstuberCommented:
I agree switching to CBO from RBO is a good idea,
 but it's not actually related to the specific reason why query 2 is better than query 1.

Since you're able to use the RANK analytic that means you're using at least 8.1  so CBO is definitely an option to investigate.
0
 
slightwv (䄆 Netminder) Commented:
>>but it's not actually related to the specific reason why query 2 is better than query 1.

As they are currently written, I agree and should have commented on that.

enrique_aeo,
please do not award any points to my post on RBO versus CBO.

0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now