This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
17th International Conference on Database and Expert Systems Applications (DEXA'06)
Checking Integrity Constraints - How it Differs in Centralized, Distributed and Parallel Databases
Krakow, Poland
September 04-September 08
ISBN: 0-7695-2641-1
Hamidah Ibrahim, Universiti Putra Malaysia, Malaysia
An important aim of a database system is to guarantee database consistency, which means that the data contained in a database is both accurate and valid. Integrity constraints represent knowledge about data with which a database must be consistent. The process of checking constraints to ensure that update operations or transactions which alter the database will preserve its consistency has proved to be extremely difficult to implement, particularly in distributed and parallel databases. In distributed databases the aim of the constraint checking is to reduce the amount of data needing to be accessed, the number of sites involved and the amount of data transferred across the network. In parallel databases the focus is on the total execution time taken in checking the constraints. This paper highlights the differences between centralized, distributed and parallel databases with respect to constraint checking.
Citation:
Hamidah Ibrahim, "Checking Integrity Constraints - How it Differs in Centralized, Distributed and Parallel Databases," dexa, pp.563-568, 17th International Conference on Database and Expert Systems Applications (DEXA'06), 2006
Usage of this product signifies your acceptance of the Terms of Use.