Language features for flexible handling of exceptions in information systems
ACM Transactions on Database Systems (TODS)
Data quality and due process in large interorganizational record systems
Communications of the ACM
Extending a relational database with deferred referential integrity checking and intelligent joins
SIGMOD '89 Proceedings of the 1989 ACM SIGMOD international conference on Management of data
Deriving production rules for constraint maintenance
Proceedings of the sixteenth international conference on Very large databases
Data warehouse: practical advice from the experts
Data warehouse: practical advice from the experts
Building, using, and managing the data warehouse
Building, using, and managing the data warehouse
Improving data warehouse and business information quality: methods for reducing costs and increasing profits
Data Quality for the Information Age
Data Quality for the Information Age
Semantic Integrity Dependencies and Delayed Integrity Checking
VLDB '82 Proceedings of the 8th International Conference on Very Large Data Bases
Compiling a Declarative High-Level Language for Semantic Integrity Constraints
DS-6 Proceedings of the Sixth IFIP TC-2 Working Conference on Data Semantics: Database Applications Semantics
AIM - An Integrity Monitor for the Database System INGRES
VLDB '83 Proceedings of the 9th International Conference on Very Large Data Bases
| Hi-index | 0.00 |
Despite many years of research into mechanisms for checking integrity in databases, current commercial systems provide support for checking only the simplest forms of integrity constraints. However, both the users and developers of database applications are increasingly aware of the problems that can arise when poor quality data is allowed to enter, and remain within, large scale databases. Clearly, some form of integrity checking is required for such applications, but it must be packaged in a way that respects the business context in which the application is to operate. In particular, this means acknowledging that mission critical transaction processing cannot be delayed while integrity checks are made. In this paper, we propose an approach which makes use of periods of low database activity for integrity checking.We present a range of algorithms for scheduling integrity checks during these periods, and describe the results of our initial experiments with the system.