Making an object-oriented DBMS active: Design, implementation, and evaluation of a prototype
Extant databases are passive in nature and offer little or no support for automatically monitoring conditions defined over the state of the database. In fact such a capability is central for a variety of applications requiring timely and time-constrained data management and processing (e.g., cooperative processing, process control, air traffic control, threat analysis).
Traditionally, the effect of condition monitoring has been realized either by encoding condition evaluation as part of the application program or by polling the database (periodically) for condition evaluation. This paper explores a third alternative, viz. active condition monitoring from an object-oriented design perspective. The focus of this paper is on the design and implementation of active condition monitoring functionality for an object-oriented Database Management System (DBMS) and its evaluation: performance comparison with polling, influence of implementation strategies on performance, and identification of opportunities for optimization.
KeywordsCondition Monitoring Object Class Active Object Defense Advance Research Project Agency Multiple Rule
Unable to display preview. Download preview PDF.
- [BOBR83]Bobrow, D. G., Stefik, M., "The Loops Manual", Intelligent Systems laboratory, Xerox Corporation, 1983.Google Scholar
- [CHAK89]S. Chakravarthy, B. Blaustein, et al, "HiPAC: A Research Project in Active, Time-Constrained Database Management", Final Technical Report, Xerox Advanced Information Technology Division, July 1989.Google Scholar
- [DARN87]Darnovsky, M., and Bowman, J., "TRANSACT-SQL USER'S GUIDE", Document 3231-2.1, Sybase Inc., 1987.Google Scholar
- [DAYA88a]Dayal, U., et al., "The HiPAC Project: Combining Active Databases and Timing Constraints", ACM Sigmod Record, March 1988.Google Scholar
- [DAYA88b]Dayal, U., et al., "HiPAC: A Research Project in Active, Time-Constrained Database Management", Interim Report (CCA-88-02), June 1988.Google Scholar
- [DAYA87a]Dayal, U., Goldhirsch, D., Orenstein, J., and DeWitt, M., "PROBE Final Report", Draft, CCA, November 1987.Google Scholar
- [DAYA87b]Dayal, U., et al., "Overview of PROBE: An Object-Oriented, Extensible Database System", To appear in IEEE Expert.Google Scholar
- [DITT86]Dittrich, K. R., Kotz, A. M., and Mulle, J. A., "An Event/Trigger Mechanism to Enforce Complex Consistency Constraints in Design Databases", SIGMOD Record, Vol. 15, No. 3, 1986, pp. 22–36.Google Scholar
- [INTE85]IntelliCorp, "KEE Software Development System User's Manual", IntelliCorp, Mountain View, 1985.Google Scholar
- [MANO86]Manola, F. A., and Dayal, U., "PDM: An Object-Oriented data Model", Proceedings of International Workshop on Object-Oriented Database Systems, 1986.Google Scholar
- [ROSE86]Rosenthal, A., Heiler, S., Dayal, U., and Manola, F. A., "Traversal Recursion: A Practical approach to Supporting Recursive Applications", Proceedings ACM SIGMOD, 1986.Google Scholar
- [STON86]Stonebraker, M., Rowe, L., "The Design of POSTGRES", Proceedings of ACM-SIGMOD, 1986, pp. 340–355.Google Scholar
- [STON87]Stonebraker, M., Hanson, M., and Potamianos, S., "A Rule manager for Relational database Systems", Technical Report, Dept. of Electrical Engineering and Computer Science, Univ. of California, Berkeley, 1987.Google Scholar