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.
|Original language||English (US)|
|Number of pages||3|
|Journal||Proceedings of the ACM SIGMOD International Conference on Management of Data|
|State||Published - 2005|
|Event||SIGMOD 2005: ACM SIGMOD International Conference on Management of Data - Baltimore, MD, United States|
Duration: Jun 14 2005 → Jun 16 2005