Principles of transaction-oriented database recovery

@article{Haerder1983PrinciplesOT,
  title={Principles of transaction-oriented database recovery},
  author={Theo Haerder and Andreas Reuter},
  journal={ACM Comput. Surv.},
  year={1983},
  volume={15},
  pages={287-317}
}
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… 
Selective Recovery for Long-Duration Transactions in Object-Oriented Database Management Systems
Long-duration transactions play an important role in non-standard database applications like design environments or office automation. This paper deals with recovery for long-duration transactions.
Performance analysis of recovery techniques
TLDR
A set of analytic models is introduced and evaluated in order to compare the performance characteristics of nine different recovery techniques with respect to four key parameters and a set of other parameters with less influence.
Isolation of transaction aborts in object-oriented database systems
TLDR
This work defines the notion of strict schedules for object-oriented databases as an extension of the analogous definition for read and write operations and shows that strict schedules possessing this property possess the recovery isolation property.
A survey of B-tree logging and recovery techniques
  • G. Graefe
  • Computer Science
    ACM Trans. Database Syst.
  • 2012
TLDR
Central in this discussion are physical data independence, separation of logical database contents and physical representation, and the concepts of user transactions and system transactions.
An Implementation of Transaction Logging and Recovery in a Main Memory Resident Database System
This report describes an implementation of Transaction Logging and Recovery using Unix Copy-On-Write on spawned processes. The purpose of the work is to extend WS-Iris, a research project on Object
An efficient recovery scheme for locking-based distributed database systems
  • Junguk L. Kim, T. Park
  • Computer Science
    Proceedings of IEEE 13th Symposium on Reliable Distributed Systems
  • 1994
This paper presents a checkpointing recovery scheme which effectively copes with media failures in distributed database systems, under the two-phase locking policy. Our scheme utilizes both the
Recovering Active Databases
  • O. Zukunft
  • Computer Science
    Rules in Database Systems
  • 1995
TLDR
This paper examines which conclusions must be drawn for the active part of the DBMS if the authors take into account that a DBMS might fail and needs to be recovered, and proposes techniques for handling different kinds of failures.
Incremental restart (database management)
  • Eliezer Levy
  • Computer Science
    [1991] Proceedings. Seventh International Conference on Data Engineering
  • 1991
TLDR
It is argued that the unique ways stable memory is used and the structure that is imposed on the log are steps in the right direction in the anticipated evolution of recovery management.
Functionality and architecture of a cooperative database system: a vision
TLDR
A database system fostering the cooperative usage and modification of a common data pool should provide standard database functionality plus means for a step-wise, cooperative refinement of data over a long period of time.
Rolling Back in a Selective Way An Approach to Recovery for Interactive and Long-Running Transactions
Universita¨t-GH EssenSchu¨tzenbahn 70, D-45117 Essenunlandr@informatik.uni-essen.deAbstractInteractive and long-running transactions are an important concept in non-standarddatabase applications
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 75 REFERENCES
Performance analysis of recovery techniques
TLDR
A set of analytic models is introduced and evaluated in order to compare the performance characteristics of nine different recovery techniques with respect to four key parameters and a set of other parameters with less influence.
Recovery Techniques for Database Systems
A survey of techniques and tools used in filing systems, database systems, and operating systems for recovery, backing out, restart, the mamtenance of consistency, and for the provismn of crash
Recovery semantics for a DB/DC system
TLDR
A unified, systematic view of integrity/recovery as it relates to a data-processing system—whether man, machine, or both is presented.
Differential files: their application to the maintenance of large databases
TLDR
This paper describes a differential database representation which is shown to be an efficient method for storing large and volatile databases.
The Recovery Manager of the System R Database Manager
TLDR
The recovery subsystem of an experimental data management system is described and evaluated and the DO-UNDO-REDO protocol allows new recoverable types and operations to be added to the recovery system.
A Fast Transaction-Oriented Logging Scheme for Undo Ro overy
  • A. Reuter
  • Computer Science
    IEEE Transactions on Software Engineering
  • 1980
A special UNDO log algorithm combining the advantages of update in place strategies with the shadow page concept is introduced. It is to support applications demanding high rates of possibly long
Physical integrity in a large segmented database
TLDR
A recovery scheme is first proposed for system failure (hardware or software error which causes the contents of main storage to be lost) and a facility for protection against damage to the auxiliary storage itself is proposed.
A Survey of Techniques for Synchronization and Recovery in Decentralized Computer Systems
TLDR
The proposed approach to solving the recovery of objects in spite of user errors, application errors, or partial system failure is based on a software structuring abstraction called the atonuc action, a type of generalized transaction.
The notions of consistency and predicate locks in a database system
TLDR
It is argued that a transaction needs to lock a logical rather than a physical subset of the database, and an implementation of predicate locks which satisfies the consistency condition is suggested.
Retrospection on a database system
This paper describes the implementation history of the INGRES database system. It focuses on mistakes that were made in progress rather than on eventual corrections. Some attention is also given to
...
1
2
3
4
5
...