Re: dbms_refresh
- From: Jared Still <jkstill@xxxxxxxxx>
- To: Chuck Boddy <Chuck.Boddy@xxxxxxxxxxxxxxx>
- Date: Wed, 13 Oct 2010 13:26:27 -0700
On Wed, Oct 13, 2010 at 12:56 PM, Chuck Boddy
<Chuck.Boddy@xxxxxxxxxxxxxxx>wrote:
> Yep…I hear you…there is a reason for the trigger over a nested MV…..try
> to put in a nutshell…the refresh group has 2 layers…”core” materialized
> views(simple snapshots)…and nested materialized views(some that are
> refreshed based on another materialized views log table)…the trigger is off
> of the simple snapshot from a core table because it will have the most
> current data..once the refresh is complete….the aggregate table needs to
> have the most current data…the user that uses the table needs the most
> current data….hard to explain in an email thread…but there’s a reason to go
> with the trigger….fun stuff…
>
>
Thanks for the explanation.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
Other related posts:
