Think of the materialized view as a table that needs to be refreshed
regularly. If you know how to deal with how and where to place tables,
the same goes for the MVs. Look up "fast refreshable" materialized
views, especially when dealing with large amount of data.
C Chang <cschang_at_maxinter.net> wrote in message news:<3E7AA4B1.31F8_at_maxinter.net>...
> Our 8.1.6 DB is on NT 4 with 2 CPU and 6x8 G HD on RAID. I like to
> build a Materialized View for Reporting purpose. So generally, for
> better performance, the materialized View is built on the current DB
> schema or another schema for this? Can anyone share their experience?
> The Materialized View that I design is REFRESH once a day in the 2 AM.
> It will collect almost half of the records of the current DB, roughly
> 400 MB. This is the first Materialized View I EVER do.
>
> C Chang
Received on Fri Mar 21 2003 - 11:14:59 CST
