Hi all,
I'm evaluating materialized views to build summary tables and I've run in a pretty hard problem.
My materialized view is based on a complex view, so I can't refresh FAST ON COMMIT, the source view will contain a LOT of rows so some delta update is mandatory.
I'm evaluating the use of a partitioned mv as a workaround, but I'm not shure about the chance to reload/refresh only a partition.
Can this be a solution, or I'll have better use a partitioned table and truncate/reload only the partition of interest?
I hope that my description of the problem is clear enough.
Thanks in advance for any help!!!
Stick to your guns
I'm evaluating materialized views to build summary tables and I've run in a pretty hard problem.
My materialized view is based on a complex view, so I can't refresh FAST ON COMMIT, the source view will contain a LOT of rows so some delta update is mandatory.
I'm evaluating the use of a partitioned mv as a workaround, but I'm not shure about the chance to reload/refresh only a partition.
Can this be a solution, or I'll have better use a partitioned table and truncate/reload only the partition of interest?
I hope that my description of the problem is clear enough.
Thanks in advance for any help!!!
Stick to your guns