Institute for Systems Research

Permanent URI for this communityhttp://hdl.handle.net/1903/4375

Browse

Author: search.filters.author.Roussopoulos, N.Subject: search.filters.subject.databases

Search Results

Now showing 1 - 3 of 3
  • Thumbnail Image
    Item
    ICON: A System for Implementing Constraints in Object-based Networks
    (1994) Goli, Shravan K.; Haritsa, Jayant R.; Roussopoulos, N.; ISR; CSHCN
    In today's Network Management scenario, the network operator's interface to the network is through a Management Information Base (MIB). The MIB stores all management related data such as configuration information, performance statistics, and trouble logs and so on. Configuration management, which is at the core of network management, is implemented through the MIB in a three step process: making updates to MIB data elements, checking the validity of the updates, propagating the effects of the updates to the network elements. While all three steps need to be executed efficiently for the MIB to serve its intended goal, the second step of checking update validity is especially important from the management viewpoint. For example, if an operator mistakenly configures a ninth port on an eight port card, it is essential that the MIB should both detect and prevent this error. Allowing such operations to go through would have adverse impact on the performance of the network (since it increases the network management traffic). Therefore, we focus primarily on the problem of checking the validity of updates to MIB data elements, which can be viewed as a specific instance of the general problem of constraint management in database systems. We introduce the design of ICON (Implementing Constraints in Object-based Networks), a proposed constraint management system. In ICON, constrains are expressed through rules. Each rule is composed of an event, a condition, and an action. Occurrence of the event triggers the rule, the condition is a boolean check, and the action is executed if the condition is satisfied. Rules and events are also treated as objects so that they can be created, modified, and deleted like other objects, thus providing a uniform view of rules and events in an OO context. The OO paradigm results in an extensible and a reusable system. To our knowledge, not much work has been done in this area and this paper would trigger further research in this area.
  • Thumbnail Image
    Item
    MANDATE: MAnaging Networks using DAtabase TEchnology
    (1992) Haritsa, Jayant R.; Ball, Michael O.; Roussopoulos, N.; Datta, Anindya; ISR
    In a recent opinion poll of telecommunications executives, enterprise network management was identified to be the top technological issue of the future. At present, however, there do not exist any viable solutions to this critical problem. Therefore, considerable research efforts are being focused on the development of effective network management tools. A management information database is the heart of a network management system - it provides the interface between all functions of the network management system, and therefore has to provide sophisticated functionality allied with high performance. In this paper, we describe MANDATE (MAnaging Networks using DAtabase TEchnology), a database system that is designed to effectively support the management of large networks of the future. MANDATE uses special characteristics of network management data and transactions, together with recent advances in database technology, to efficiently derive its functionality.
  • Thumbnail Image
    Item
    Update Dependencies in the Relational Model
    (1991) Mark, Leo; Roussopoulos, N.; Cochrane, Roberta J.; ISR
    Relational database systems suffer from the lack of a rich update language. In this paper we present the Update Dependency Language which allows the database designer to specify a procedure for each update that is activated when attempts are made to perform the update. Each procedure integrates the update dependencies for an update and provides an operational semantics for the update which is maintained by the system. We provide a formal definition for this language, illustrate its use, and discuss concurrency control issues related to integrating such a language into a database system.