Efficiently updating materialized views
SIGMOD '86 Proceedings of the 1986 ACM SIGMOD international conference on Management of data
SIGMOD '86 Proceedings of the 1986 ACM SIGMOD international conference on Management of data
Extending a database system with procedures
ACM Transactions on Database Systems (TODS)
Efficiently supporting procedures in relational database systems
SIGMOD '87 Proceedings of the 1987 ACM SIGMOD international conference on Management of data
A performance analysis of view materialization strategies
SIGMOD '87 Proceedings of the 1987 ACM SIGMOD international conference on Management of data
Database abstractions: aggregation and generalization
ACM Transactions on Database Systems (TODS)
SIGMOD '84 Proceedings of the 1984 ACM SIGMOD international conference on Management of data
Efficient support for rules and derived objects in relational database systems
Efficient support for rules and derived objects in relational database systems
Performance enhancement through replication in an object-oriented DBMS
SIGMOD '89 Proceedings of the 1989 ACM SIGMOD international conference on Management of data
Function materialization in object bases
SIGMOD '91 Proceedings of the 1991 ACM SIGMOD international conference on Management of data
Evaluation of relational algebras incorporating the time dimension in databases
ACM Computing Surveys (CSUR)
Function Materialization in Object Bases: Design, Realization, and Evaluation
IEEE Transactions on Knowledge and Data Engineering
RPL: An Expert System Language with Query Power
IEEE Expert: Intelligent Systems and Their Applications
A Performance Study of Query Optimization Algorithms on a Database System Supporting Procedures
VLDB '88 Proceedings of the 14th International Conference on Very Large Data Bases
| Hi-index | 0.00 |
A database procedure is a collection of queries stored in the database. Several methods are possible for processing queries that retrieve the value returned by a database procedure. The conventional algorithm is to execute the queries in a procedure whenever it is accessed. A second strategy requires caching the previous value returned by the database procedure. If the cached value is valid at the time of a query, the value is returned immediately. If the cached value has been invalidated by an update, the value is recomputed, stored back into the cache, and then returned. A third strategy uses a differential view maintenance algorithm to maintain an up-to-date copy of the value returned by the procedure. This paper compares the performance of these three alternatives. The results show that which algorithm is preferred depends heavily on the database environment, particularly, the frequency of updates and the size of objects retrieved by database procedures.