Materialized View - Is it better than using triggers?
415437Mar 8 2005 — edited Mar 10 2005In one of my applications I used to have a view. Quite a few of the complex queries were based on this view and We had found that these were quite slow. Hence instead of using this view, we created a table in the next version and added triggers on the base table to populate this new table. By doing this the queries are a lot faster when run against this new table.
I did not know at all (and still don't know much) about materialized views when I changed the above view to a table. Now reading little bit about the materialized views, I am thinking whether I should get rid of the triggers and have a materialized view for my scenario. Can anybody guide me to the pros / cons of using materialized view instead of a table kept in sync using triggers.
Personally I am in favour of getting rid of the triggers as they are quite complicated.
Any thoughts will be appreciated.