Hilfe Wegweiser Datenschutzhinweis Impressum Kontakt





Transaction Time Support Inside a Database Engine


Shegalov,  German
Databases and Information Systems, MPI for Informatics, Max Planck Society;

Externe Ressourcen
Es sind keine Externen Ressourcen verfügbar
Volltexte (frei zugänglich)
Es sind keine frei zugänglichen Volltexte verfügbar
Ergänzendes Material (frei zugänglich)
Es sind keine frei zugänglichen Ergänzenden Materialien verfügbar

Lomet, D. B., Barga, R. S., Mokbel, M. F., Shegalov, G., Wang, R., & Zhu, Y. (2006). Transaction Time Support Inside a Database Engine. In Proceedings of the 22nd International Conference on Data Engineering (ICDE 2006) (pp. 1-12). Los Alamitos, USA: IEEE.

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.