Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Critical Qs on materialized views

Critical Qs on materialized views

From: VIVEK_SHARMA <VIVEK_SHARMA_at_infosys.com>
Date: Fri, 26 Aug 2005 16:47:18 +0530
Message-ID: <B5587533FCBD4344ADB8290B3EDDA1220883A6DB@kecmsg14.ad.infosys.com>

Thomas, folks

Is there some way of Avoiding creation of Constraint on Source/Master table while using Materlialized view refresh? NOTE - Production Database does NOT have any constraints & is of 600 GB

Creation of constraints on Source/Master DB Tables would be very time consuming, if attempted.

Thanks indeed for the info.

-----Original Message-----

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Thomas Day Sent: Thursday, August 25, 2005 10:10 PM To: oracle-l_at_freelists.org
Subject: Re: Some Basic Qs on materialized views

It's not the size of the database that determines how often you refresh the materialized views. Rather, it's the frequecy with which the data changes on the source database and how important it is to the business that that data is reflected in the target database in a timely fashion.

We used 15 minutes for transaction oriented tables, 1 hour for tables that were less volatile and 24 hours for look-up tables (e.g., country_codes) where the table's content was only changed via a software change request.

We used dbms_jobs to schedule and fire the refreshes.
--

http://www.freelists.org/webpage/oracle-l

Received on Fri Aug 26 2005 - 06:52:14 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US