Abstract

 
 
 This paper presents a solution to check referential integrity constraints and conjunctive global constraints in a relational multi database system. It also presents the experimental results obtained by implementing this solution over a PC cluster with Oracle9i DBMS.
 The goal of those experimentations is to measure the time spent to check global constraints in a distributed systems. The results show that the overhead induced by our distributed constraint checking is reduced by 50% compared to a centralized checking of constraints.
 
 
Highlights
Multidatabase Systems (MDBS), where different sites, connected by large scale (e.g. Internet) or local (e.g. Fast Ethernet) network, store parts of a global database are nowadays widely used: distributed databases, database clusters, mediation based systems, databases over peer-to-peer networks
In [2], we propose a classification of integrity constraint and give, for each constraint type, strategies for integrity checking in an object oriented multidatabase, according to the nodes on which updates are sent
We first focus on referential integrity constraints, we address global conjunctive constraints which are a generalization of referential integrity constraints
Summary
Multidatabase Systems (MDBS), where different sites (or nodes), connected by large scale (e.g. Internet) or local (e.g. Fast Ethernet) network, store parts of a global database are nowadays widely used: distributed databases, database clusters, mediation based systems, databases over peer-to-peer networks. An integrity constraint may be local, i.e. it relates data stored on a single node. Otherwise, it is a global constraint, i.e. it relates data distributed over different sites. Maintaining global constraints is a challenging performance issue, since it involves a distributed evaluation for checking the constraints. Data involved by such a constraint being distributed over various nodes, it is necessary to determine on which node(s) the constraint must be checked to minimize the checking process duration, by minimizing the quantity of information transferred through the network, and optimize transaction response time. In [2], we propose a classification of integrity constraint and give, for each constraint type, strategies for integrity checking in an object oriented multidatabase, according to the nodes on which updates are sent
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
