Comparison of Access Methods for TimeEvolving Data时间演化数据访问方法的比较.pptVIP

Comparison of Access Methods for Time-Evolving Data Betty Salzberg and Vassilis Tsotras CS599, Temporal and Spatial Databases Course. Presented by: Atousa Golpayegani 11/16/2000 Temporal database design problem Temporal database design problem Outline Brief introduction to temporal databases Criteria for comparison of access methods Efficient method design for transaction/Bitemporal data Method classification and comparison Conventional Vs. Temporal Databases Conventional database captures only a single snapshot of the modeled reality, usually the most current. Can not support past and future data. Ex: “ the current salary of an employee”. Temporal database supports some time domain and is thus able to manage time varying data. User-defined time is excluded. Ex: “ the current and the previous salaries of an employee since hiring”. What is Stored in a Temporal Database? Tuple-versioning Temporal model is used. In this model Database is a set of records that store the versions of the real life objects. Each record has: A time invariant key A number of time variant attributes (for simplicity just one) One or two intervals Start time End time Ex: Employee (ss#, name, salary, [t1, now) ) Taxonomy of Time in a Temporal Database Transaction Time Is defined as the time when a fact is stored in the database. Valid Time Is defined as the time when a fact becomes effective (valid) in reality. Bitemporal Time Is the combination of the above two types. Time is assumed to be discrete, and consecutive nonnegative integers Any change is assumed to occur only at an indicated time Addition of an object Deletion of an object Value change of an object’s attribute Transaction Time Database Time Interval shows when an object was added and deleted. An object is alive from the time it is added to the database until it is deleted. Ex. Object ‘a’ is the only one that is currently alive. No record is physically deleted (logical deletion). Therefore databa