TY - GEN
T1 - Transaction time support inside a database engine
AU - Lomet, David
AU - Barga, Roger
AU - Mokbel, Mohamed F.
AU - Shegalov, German
AU - Wang, Rui
AU - Zhu, Yunyue
PY - 2006
Y1 - 2006
N2 - Transaction time databases retain and provide access to prior states of a database. An update "inserts" a new record while preserving the old version. Immortal DB builds transaction time database support into a database engine, not in middleware. It supports as of queries returning records current at the specified time. It also supports snapshot isolation concurrency control. Versions are stamped with the "clock times" of their updating transactions. The timestamp order agrees with transaction serialization order. Lazy timestamping propagates timestamps to transaction updates after commit. Versions are kept in an integrated storage structure, with historical versions initially stored with current data. Time-splits of pages permit large histories to be maintained, and enable time based indexing, which is essential for high performance historical queries. Experiments show that Immortal DB introduces little overhead for accessing recent database states while providing access to past states.
AB - Transaction time databases retain and provide access to prior states of a database. An update "inserts" a new record while preserving the old version. Immortal DB builds transaction time database support into a database engine, not in middleware. It supports as of queries returning records current at the specified time. It also supports snapshot isolation concurrency control. Versions are stamped with the "clock times" of their updating transactions. The timestamp order agrees with transaction serialization order. Lazy timestamping propagates timestamps to transaction updates after commit. Versions are kept in an integrated storage structure, with historical versions initially stored with current data. Time-splits of pages permit large histories to be maintained, and enable time based indexing, which is essential for high performance historical queries. Experiments show that Immortal DB introduces little overhead for accessing recent database states while providing access to past states.
UR - http://www.scopus.com/inward/record.url?scp=33749644509&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=33749644509&partnerID=8YFLogxK
U2 - 10.1109/ICDE.2006.162
DO - 10.1109/ICDE.2006.162
M3 - Conference contribution
AN - SCOPUS:33749644509
SN - 0769525709
SN - 9780769525709
T3 - Proceedings - International Conference on Data Engineering
SP - 35
BT - Proceedings of the 22nd International Conference on Data Engineering, ICDE '06
T2 - 22nd International Conference on Data Engineering, ICDE '06
Y2 - 3 April 2006 through 7 April 2006
ER -