RE: Oracle Total Recall performance vs Materialized Views
Date: Mon, 29 Jul 2013 13:53:35 -0400
Message-ID: <C1117B1AA0340645894671E09A7891F71512B8EBE9_at_EIHQEXVM2.ei.local>
Putting the set of tables in a refresh group is not an option? I understood that a consistent refresh of the set was possible.
Joel Patterson
Database Administrator
904 928-2790
--
Joel Patterson
Sr. Database Administrator | Enterprise Integration
Phone: 904-928-2790 | Fax: 904-733-4916
http://www.entint.com/
http://www.facebook.com/pages/Enterprise-Integration/212351215444231 http://twitter.com/#!/entint http://www.linkedin.com/company/18276?trk=tyah http://www.youtube.com/user/ValueofIT
This message (and any associated files) is intended only for the use of the addressee and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient, you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from us may be monitored. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company. [v.1.1]
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Guillermo Alan Bort
Sent: Monday, July 29, 2013 12:00 PM
To: oracle-l-freelists
Subject: Oracle Total Recall performance vs Materialized Views
Hi,
We are having a discussion about the following:
we have a set of tables, from these tables we need to have a snapshot of the table at 00:00:00 exactly (all the tables at the same time). Right now we are using materialized views and we refresh them nightly. Of course this is a weak solution as if any refresh fails, we loose consistency.
as I don't like square wheels and the architect can't seem to build a round one, I suggested using Oracle Total Recall, which based on the documentation does everything we need (including guaranteeing consistency and stuff like that).
The architect claims that the performance on the queries with flashback (with FDA enabled) is unacceptable for the application. I am certain he didn't perform any testing, and I will do so as soon as I finish building the environment, but I'm sure there are some people out there who have already implemented total recall in production so my question to you is what is the performance overhead of FDA (I've read about the overhead during commit, and the restriction regarding DDLs; I'm wondering about the performance of queries).
Thank you very much,
Alan.-
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jul 29 2013 - 19:53:35 CEST