On pure OLTP these are rarely if at all needed. As for hybrids (which
are almost all of systems) it may benefit reporting part of the
application at some expense for OLTP part.
Most limiting IMHO is using REFRESH ON COMMIT for "summaries", i.e. when
some aggregates need to be updated online. Usually may lead to excessive
TX locks when two or more transactions are updating different rows of
underlying table, which are the inputs for the same single row in the
summary.
HTH
- Andrey
HI
*IT IS BENIFICIAL TO HAVE MATEREIALIZED VIES IN OLTP SYSTEM *
*PLEASE HELP ME *
Thanks & Regards
Sachin Sethi
Software Engineer
Telserra , Gurgaon
Suite 501, 5th floor,
Pacific Squre, 32nd Milestone,
NH - 8, Gurgaon -122 001,
India, Tel: - +91-124-411-7071, Fax: +91-124-411-7079
Mobile : +919899595255
E-Mail :s.sethi@xxxxxxxxxxxx
URL: www.telserra.com <http://www.telserra.com>