If you just need a VIEW, then you can do what William is suggesting.

If you need Materialized view, then this implies you have summary data
you want stored, and the data needs to be readily available (not just a
link to another table, as a regular view is)

To do this, you'll first need to know what the summary data is, and then
set up the database to handle materialized views.

The View that William suggested is just a stored SQL statement. A
Materialized view actually allocates space to hold summary and detail
data, plus the query rewriting system and the synchronization system
(M$LOG) needs to be set up in advance.



-----Original Message-----
From: BRoussel
[mailto:oracledba-ezmlmshield-x17342744.[Email address protected]
Sent: Monday, October 31, 2005 12:11 PM
To: LazyDBA Discussion
Subject: Materialized Views





Hi DBAs,

I would like to use materialized views for a project that we are
thinking of, see below:

2 tables with 4.4 millions of rows each
Need to be read-only view
Run from Monday to Friday at 5:00am

It is my first time and I would like to have an example on how to
code this materialized view...

The environment is Unix Solaris and Oracle9i.

Thanks,

Bruno



--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com To unsubscribe:
see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com By using this list you agree
to these terms:http://www.lazydba.com/legal.html


Oracle LazyDBA home page