Re: Materialized View vs. Manual summary job

Hi Christian,

Look into Materilaized view log and become familiar with the concept of "fast refresh", "complete refresh" and "query rewrite". Materialized can help you in several ways. It shedules a job to update your datamart so you don't have to do it manually. Also, if fast refresh is possible, it will of course improve the loading performance. If "query rewrite" kicks in during your querying the datamart, the response time will improve.

BTW, are you using any third party OLAP tool? Or are you just using SQL*PLUS to generate reports out of the datamart?

John

chse30_at_hotmail.com (Christian Svensson) wrote in message news:<ccc2a7eb.0308290252.f72808d_at_posting.google.com>...
> Greetings all,
>
> We are currently in our Datawarehouse project using manual jobs to
> create summay tables for our datamarts. I am about to investigate if
> we can gain some performance of using Materialized Views(MV) to do the
> summary tables so to say. The datamarts affected by this are always
> inital load and not delta loads. The jobs are run every weekend.
>
> - Are there any performance gains using MVs to handle the summary
> tables creation versus to manual in a Sql job do the summary ?
>
> - When new daily data arrives in our fact table, does the MVs refresh
> engine only do a new summary of only the newly arrived data or does it
> do a complete refresh ? (The anwser to this is directly affected the
> above...)
>
> Our environment is Solaris & Oracle 8.1.7.3
>
> Thanks for any comments on this.
>
> Best regards
>
> Christian Svensson
Received on Fri Aug 29 2003 - 10:43:35 CDT