|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
|
|
#1
November 17th, 2004, 05:53 PM
|
|||
|
|||
Materialized view
What is the difference between Materialized view and normal view in Oracle? If I replace the Materialzed view by the normal one then what problems I am going to face.
The syntax for my materialized view is: create materialised view Image CACHE as query....
|
|
#2
November 19th, 2004, 04:10 PM
|
|||
|
|||
|
I believe that a Materialised view is not actually a view (in oracles nornal sense of the word) but is actually just another type of table. MViews replace the SNAPSHOTs of old.
MViews are meant to be used for scheduling large data retreaval from multiple tables (data requests the take a long time to process and where the data does not need to be 'real time') and are not designed for on-the-fly access like normal views. Typlically MViews would be updated daily while many users were not accessing the data. Most people will not require MViews, I would stick to normal Views unless you are running a data warehouse!
|
|
| Viewing: Dev Shed Forums > Databases > Oracle Development > Materialized view |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
