Immortal DB: transaction time support for SQL server

ABSTRACT

Immortal DB builds transaction time database support into the SQL Server engine, not in middleware. Transaction time databases retain and provide access to prior states of a database. An update "inserts" a new record while preserving the old version. The system supports as of queries returning records current at the specified time. It also supports snapshot isolation concurrency control. Versions are stamped with the times of their updating transactions. The timestamp order agrees with transaction serialization order. Lazy timestamping propagates timestamps to all updates of a transaction after commit. All 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. We demonstrate Immortal DB with a moving objects application that tracks cars in the Seattle area.

REFERENCES

• 1: Philip A. Bernstein , Vassco Hadzilacos , Nathan Goodman, Concurrency control and recovery in database systems, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1987
• 2: Thomas Brinkhoff, A Framework for Generating Network-Based Moving Objects, Geoinformatica, v.6 n.2, p.153-180, June 2002 [doi>10.1023/A:1015231126594]
• 3: Curtis E. Dyreson , Richard Thomas Snodgrass, Supporting valid-time indeterminacy, ACM Transactions on Database Systems (TODS), v.23 n.1, p.1-57, March 1998 [doi>10.1145/288086.288087]
• 4: David Lomet , Betty Salzberg, Access methods for multiversion data, Proceedings of the 1989 ACM SIGMOD international conference on Management of data, p.315-324, June 1989, Portland, Oregon, United States
• 5: D. B. Lomet and B. Salzberg. Temporal Databases: Theory, Design, and Implementation, chapter Transaction-Time Databases, 388--417. Benjamin/Cummings, 1993.