Hello, I am learning some about materialized view and my question is:
Could the materialized views cause some aditional consequences or problems in the normal database performance?
version: oracle 8.1.7
thanks!!!!
Printable View
Hello, I am learning some about materialized view and my question is:
Could the materialized views cause some aditional consequences or problems in the normal database performance?
version: oracle 8.1.7
thanks!!!!
It all depends on what you do with your materialized view, just as an example a simple MVIEW that gets recreated once a week when no users are hitting the database would have less impact that a complex MVIEW that gets refreshed once an hour 24x7
Thanks for your answer. But I refer about the disadvantages or bad consecuences when we use MVIEW in the database's performance. The effect in the database. I know that more complex more impact, but Are there "Colateral Effects" to I have take account?
Thanks a lot!!!!
P/D: Sorry for my english. I am Argentinian.
well... who would know Argentinian was so close a language to English :D
Would you mind in defining what would be a "collateral effect"? please note that what I've described shows two very different impacts on database performance depending on your particular MVIEW.
Also, take into consideration you shouldn't resort to MVIEWs because they have a cool name, you resort to them when you really need them.
go through the links about materialized views
http://www.akadia.com/services/ora_m...zed_views.html
http://www.oreillynet.com/pub/a/orei...cle8_0600.html