RE: query performance - getting started

No extra cost options installed.   Will look into results cache.


Joel Patterson
Database Administrator
904 727-2546

________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Timo Raitalaakso
Sent: Thursday, April 07, 2011 3:14 PM
To: Patterson, Joel
Cc: Patterson, Joel; <oracle-l@xxxxxxxxxxxxx>; <kylelf@xxxxxxxxx>
Subject: Re: query performance - getting started


Do you have partitioning available? Take a look on partition change tracking 
and PCT refresh.

Timo Raitalaakso
http://rafudb.blogspot.com

<Joel.Patterson@xxxxxxxxxxx<mailto:Joel.Patterson@xxxxxxxxxxx>> kirjoitti 
7.4.2011 kello 15.50:

Query performance continued.

We have a very complicated Materialized view, and a view that utilizes the MV.  
 We cannot use Fast refresh - a complete refresh is necessary.   The app can 
decide when the view is refreshed, and can execute dbms_refresh when necessary.

Essentially all records are truncated, and the view is rebuilt as part of the 
complete refresh.    So, is this just as easy, efficient as any other method 
such as Temp tables, Truncating a permanent table and re-inserting, or other?


Moving forward,

JP

Other related posts: