RE: query performance - getting started

From: <>
Date: Thu, 7 Apr 2011 15:34:51 -0400
Message-ID: <>

Thanks to some comments by Ellis Miller, I will be upgrading one of my databases to 11g and investigation the results cache feature as it might prove to be viable.

Joel Patterson
Database Administrator
904 727-2546

From: Jorgensen, Finn [] Sent: Thursday, April 07, 2011 1:48 PM
To: Patterson, Joel; '' Subject: RE: query performance - getting started

Last time I looked into MV refreshes (in 10gR2) they did not do truncates. They do a delete of all rows. I assume this is so running queries aren't interrupted by the refresh.

So, if you have the luxury of doing a truncate and then insert (append) or better yet, drop table and CTAS, and the table is large, then that would be faster.


From: [] On Behalf Of Sent: Thursday, April 07, 2011 8:51 AM
To:; Cc:
Subject: RE: query performance - getting started

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,


>>> This e-mail and any attachments are confidential, may contain legal,
professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2

Received on Thu Apr 07 2011 - 14:34:51 CDT

Original text of this message