The Starburst active database rule system

Abstract

This paper describes our development of the Starburst Rule System, an active database rules facility i n tegrated into the Starburst extensible relational database system at the IBM Almaden Research Center. The Starburst rule language is based on arbitrary database state transitions rather than tuple-or statement-level changes, yielding a clear and exible execution semantics. The rule system has been implemented completely. Its rapid implementation was facilitated by the extensibility features of Starburst, and rule management and rule processing is integrated into all aspects of database processing.

Evolving Triggers for Dynamic Environments

“…It ensures that, whenever a particular event is detected, the order of evaluating the conditions and executing the actions among all the triggers "awaken" by that event, conforms with the user's specifications. We re-iterate that although some prototype ADb systems, such as Starburst [20] provide the option for priorities among the triggers ( [8,15]), the commercial DBMS with active capabilities, conforming with the ANSI SQL99 standard specifications [1] do not. Since we are using Oracle 9i [2], we needed to write a separate PL/SQL routine (c.f.…”

“…The database community has provided many results on the topic of Active Databases (ADb), which manage triggers operating under the Event-Condition-Action (ECA) paradigm [8,15,20]. In the recent years there have been works incorporating ECA-like triggers in novel, highlyheterogeneous, distributed and dynamic data-driven application domains, e.g., the Web [9], peer-to-peer (P2P) systems and sensor networks [22].…”

“…In the recent years there have been works incorporating ECA-like triggers in novel, highlyheterogeneous, distributed and dynamic data-driven application domains, e.g., the Web [9], peer-to-peer (P2P) systems and sensor networks [22]. Despite the co-existence of the large body of works in ENS, CQ, Data Streams, MOD [3,5,4,6,12,11,16,10], all of which have the common need of dealing with dynamically changing information, and the rich history of ADb results [8,15,20] -there is a lack of tools that would enable using the "best of all the worlds". Namely, there is no paradigm that allows the users to seamlessly tie: (1) Detection of (composite) events obtained by monitoring continuously changing data with (2) Evaluation of conditions that are continuous queries and with (3) Dynamical adjustment of the triggers themselves -all for the purpose of executing a desired policy in a constantly evolving domain of interest.…”

ActiveXQBE: A Visual Paradigm for Triggers over XML Data

“…Several research projects have provided substantial contributions to the field of active databases (e.g., Starburst [21], Hipac [15], Reach [8], Sentinel [10]). …”

Generalized Active Agent System for Extending the Active Capabilities of Relationship Database System (RDBMS)

“…After ECA rules are specified declaratively, it is the responsibility of the DBMS to monitor the situation and trigger the rules when the condition is satisfied. There have been a number of prototypes of active database systems that have been developed, such as HiPAC [CHA89], Sentinel [CHA93], Starburst [WID96], Postgres [ST091], etc. The prototypes listed are representative of a much larger number of active database systems that have been designed using an integrated approach.…”