Integrated concurrency control and recovery mechanisms: design and performance evaluation
ACM Transactions on Database Systems (TODS)
GENESIS: An Extensible Database Management System
IEEE Transactions on Software Engineering
ACM Transactions on Database Systems (TODS)
Crash recovery in client-server EXODUS
SIGMOD '92 Proceedings of the 1992 ACM SIGMOD international conference on Management of data
Analysis of recovery in a database system using a write-ahead log protocol
SIGMOD '92 Proceedings of the 1992 ACM SIGMOD international conference on Management of data
MLR: a recovery method for multi-level systems
SIGMOD '92 Proceedings of the 1992 ACM SIGMOD international conference on Management of data
ARIES/CSA: a method for database recovery in client-server architectures
SIGMOD '94 Proceedings of the 1994 ACM SIGMOD international conference on Management of data
Transaction Processing: Concepts and Techniques
Transaction Processing: Concepts and Techniques
Starburst Mid-Flight: As the Dust Clears
IEEE Transactions on Knowledge and Data Engineering
Proceedings of the 2003 ACM SIGMOD international conference on Management of data
Inside Microsoft (r) SQL Server (tm) 2005: The Storage Engine
Inside Microsoft (r) SQL Server (tm) 2005: The Storage Engine
Locking key ranges with unbundled transaction services
Proceedings of the VLDB Endowment
An evaluation of checkpoint recovery for massively multiplayer online games
Proceedings of the VLDB Endowment
| Hi-index | 0.00 |
New hardware platforms, e.g. cloud, multi-core, etc., have led to a reconsideration of database system architecture. Our Deuteronomy project separates transactional functionality from data management functionality, enabling a flexible response to exploiting new platforms. This separation requires, however, that recovery is described logically. In this paper, we extend current recovery methods to work in this logical setting. While this is straightforward in principle, performance is an issue. We show how ARIES style recovery optimizations can work for logical recovery where page information is not captured on the log. In side-by-side performance experiments using a common log, we compare logical recovery with a state-of-the art ARIES style recovery implementation and show that logical redo performance can be competitive.