I don't have a lot of experience using Materialized Views so I'd like some clarification if possible.
I have a couple of Views that users use heavily that represent self joining a table to itself from 6 to 10 times.
When called in a query, these views are adding some considerable overhead to the query run time.
Based on the answer to a previous question, I'm looking to turn them into Materialized Views.
Because they would be MV's based upon a self join, they are not considered "simple" MV's and can't be used for FAST REFRESH.
Can multiple MV's be kept updated from a single MV Log ? Will Oracle keep the updates in sync in multiple target MV's that are not simple and have to do a complete refresh ?
In the Oracle documentation (here
), under the Managing Materialized View Log Space header, it talks about " multiple simple materialized views".
Since my MV's aren't "simple", is there anything I need to be aware of ?
I don't *think* there's going to be a concern, but would like to be sure before I try to implement.
Anyone have any experience with this kind of thing ?
Thanks in advance for any insight.