Principles of transaction-oriented database recovery

In this paper, a terminological framework is provided for describing different transactionoriented recovery schemes for database systems in a conceptual rather than an implementation-dependent way. By introducing the terms materialized database, propagation strategy, and checkpoint, we obtain a means for classifying arbitrary implementations from a unified viewpoint. This is complemented by a classification scheme for logging techniques, which are precisely defined by using the other terms. It is shown that these criteria are related to all relevant questions such as speed and scope of recovery and amount of redundant information required. The primary purpose of this paper, however, is to establish an adequate and precise terminology for a topic in which the confusion of concepts and implementational aspects still imposes a lot of problems.

[1]  E. SenkoM.,et al.  Data structures and accessing in data-base systems , 1973 .

[2]  Diane C. P. Smith,et al.  Relational Data Base Machines , 1979, Computer.

[3]  Michael Stonebraker,et al.  The design and implementation of INGRES , 1976, TODS.

[4]  Butler W. Lampson,et al.  Crash Recovery in a Distributed Data Storage System , 1981 .

[5]  Guy M. Lohman,et al.  Differential files: their application to the maintenance of large databases , 1976, TODS.

[6]  Andreas Reuter,et al.  Performance analysis of recovery techniques , 1984, TODS.

[7]  Michael E. Senko,et al.  Data Structures and Accessing in Data-Base Systems. I: Evolution of Information Systems , 1973, IBM Syst. J..

[8]  Raymond A. Lorie,et al.  Physical integrity in a large segmented database , 1977, TODS.

[9]  Charles T. Davies,et al.  Recovery semantics for a DB/DC system , 1973, ACM Annual Conference.

[10]  Jim Gray,et al.  Notes on Data Base Operating Systems , 1978, Advanced Course: Operating Systems.

[11]  K. Mani Chandy,et al.  Analytic models for rollback and recovery strategies in data base systems , 1975, IEEE Transactions on Software Engineering.

[12]  Irving L. Traiger,et al.  The notions of consistency and predicate locks in a database system , 1976, CACM.

[13]  Irving L. Traiger,et al.  A history and evaluation of System R , 1981, CACM.

[14]  J. Mitchell,et al.  Issues in the design and use of a distributed file system , 1980, OPSR.

[15]  Andreas Reuter A Fast Transaction-Oriented Logging Scheme for Undo Ro overy , 1980, IEEE Transactions on Software Engineering.

[16]  Philip A. Bernstein,et al.  Concurrency Control in Distributed Database Systems , 1986, CSUR.

[17]  Andreas Reuter,et al.  Optimization of Logging and Recovery in a Database System , 1979, IFIP TC-2 Working Conference on Data Base Architecture.

[18]  CODASYL: Reports of the Data Description Language Committee , 1978, Inf. Syst..

[19]  Charles T. Davies,et al.  Data Processing Spheres of Control , 1978, IBM Syst. J..

[20]  Lawrence A. Bjork Recovery scenario for a DB/DC system , 1973, ACM Annual Conference.

[21]  C. J. Date An Introduction to Database Systems, 3rd Edition , 1977 .

[22]  Michael Stonebraker,et al.  Retrospection on a database system , 1980, TODS.

[23]  Walter H. Kohler,et al.  A Survey of Techniques for Synchronization and Recovery in Decentralized Computer Systems , 1981, CSUR.

[24]  Joost Verhofstad,et al.  Recovery Techniques for Database Systems , 1978, CSUR.

[25]  Irving L. Traiger,et al.  Granularity of Locks and Degrees of Consistency in a Shared Data Base , 1998, IFIP Working Conference on Modelling in Data Base Management Systems.

[26]  Donald D. Chamberlin A Summary of user Experience with the SQL Data Sublanguage , 1980, ICOD.

[27]  Irving L. Traiger,et al.  The Recovery Manager of the System R Database Manager , 1981, CSUR.

[28]  Tien Chi Chen Computer Technology and the Database User , 1978, VLDB.