A Comparison of Different Forms of Temporal Data Management

Künzner, Florian; Petković, Dušan

doi:10.1007/978-3-319-18422-7_8

Cited by 5 publications

(3 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Since the introduction of the temporal features in the SQL:2011 standard [58,97], major database vendors have started to implement temporal support in their database management systems [59,73,74]. Some companies realized the need for supporting temporal data earlier, and they extended their database systems with basic temporal features, such as data types, functions, and time travel queries, that make past states of a database available for querying.…”

Section: Temporal Data Support In Commercial Dbmssmentioning

confidence: 99%

Temporal Data Management – An Overview

Böhlen

Dignös

Gamper

et al. 2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Despite the ubiquity of temporal data and considerable research on the effective and efficient processing of such data, database systems largely remain designed for processing the current state of some modeled reality. More recently, we have seen an increasing interest in the processing of temporal data that captures multiple states of reality. The SQL:2011 standard incorporates some temporal support, and commercial DBMSs have started to offer temporal functionality in a step-by-step manner, such as the representation of temporal intervals, temporal primary and foreign keys, and the support for so-called time-travel queries that enable access to past states. This tutorial gives an overview of state-of-the-art research results and technologies for storing, managing, and processing temporal data in relational database management systems. Following an introduction that offers a historical perspective, we provide an overview of basic temporal database concepts. Then we survey the state-of-the-art in temporal database research, followed by a coverage of the support for temporal data in the current SQL standard and the extent to which the temporal aspects of the standard are supported by existing systems. The tutorial ends by covering a recently proposed framework that provides comprehensive support for processing temporal data and that has been implemented in PostgreSQL.

show abstract

Section: Temporal Data Support In Commercial Dbmssmentioning

confidence: 99%

Temporal Data Management – An Overview

Böhlen

Dignös

Gamper

et al. 2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…Inconsistent data are undesirable and useless". Unfortunately, mainstream DBMSs, which support temporal data management and specifically retroactive updates, like Oracle, IBM DB2 and Teradata (Künzner and Petkovic, 2015), do not provide any support for detecting or repairing inconsistencies that result from such updates. Therefore, developers of applications that require guaranteeing the database consistency after each (retroactive) update transaction on this database should proceed in an ad hoc manner in order to resolve such a problem.…”

Section: Problemsmentioning

confidence: 99%

A systematic approach to efficiently managing the effects of retroactive updates of time-varying data in multiversion XML databases

Hamrouni

Brahmia

Bouaziz

2018

IJIIDS

View full text Add to dashboard Cite

A retroactive update is an update that changes a past data. It is a common operation in both conventional and temporal databases. However, in temporal databases, a retroactive update is challenging since it could lead to data inconsistencies if the retroactively updated data were used for creating other data (like social contributions and taxes which are calculated based on the salaries of the employees). Such data inconsistencies must be repaired in order to preserve the database consistency. In this paper, we extend our previous approach on detecting and repairing automatically data inconsistencies that result from retroactive updates of multiversion temporal XML databases. The extension consists in: 1) providing an enhanced version of the architecture of our approach and explaining the process of handling a retroactive update; 2) showing how to extract data dependencies and how to use them in order to repair detected inconsistencies; 3) proposing a new log structure ensuring a complete and useful history of the executed transactions; 4) presenting a tool, named Retro-Update-Manager, that we have developed to prove technically our approach.Reference to this paper should be made as follows: Hamrouni, H., Brahmia, Z. and Bouaziz, R. (2018) 'A systematic approach to efficiently managing the effects of retroactive updates of time-varying data in multiversion XML databases', Int.

show abstract

“…Furthermore, there is no temporal query language, like TSQL2 (Snodgrass et al , 1995), or conventional query language with temporal facilities, like SQL:2011 (Kulkarni and Michels, 2012), that supports detecting and/or repairing data inconsistencies resulting from retroactive updates (Etzion et al , 1994). Moreover, although some mainstream commercial DBMSs, including Oracle, IBM DB2, Teradata and MS SQL Server, provide temporal functionalities, as surveyed in (Grandi, 2015; Künzner and Petkovic, 2015; Petkovic, 2015; Petkovic, 2016), none of them supports the management of the effects of retroactive updates on the database consistency. Notice here that, to the best of our knowledge, current ERPs (Monk and Wagner, 2013), including SAP ERP, Oracle ERP, Microsoft Dynamics, Sage Business Solutions, Infor and Epicor, do not allow the management of time-varying data.…”

Section: Introductionmentioning

confidence: 99%

Deferred repair of inconsistencies resulting from retroactive updates of temporal XML currency data

Hamrouni

Grandi

Brahmia

2017

IJWIS

View full text Add to dashboard Cite

Purpose A temporal XML database could become an inconsistent model of the represented reality after a retroactive update. Such an inconsistency state must be repaired by performing corrective actions (e.g. payment of arrears after a retroactive salary increase) either immediately (i.e. at inconsistency detection time) or in a deferred manner, at one or several chosen repair times according to application requirements. The purpose of this work is to deal with deferred and multi-step repair of detected data inconsistencies. Design/methodology/approach A general approach for deferred and stepwise repair of inconsistencies that result from retroactive updates of currency data (e.g. the salary of an employee) in a valid-time or bitemporal XML database is proposed. The approach separates the inconsistency repairs from the inconsistency detection phase and deals with the execution of corrective actions, which also take into account enterprise’s business rules that define some relationships between data. Findings Algorithms, methods and support data structures for deferred and multi-step inconsistency repair of currency data are presented. The feasibility of the approach has been shown through the development and testing of a system prototype, named Deferred-Repair Manager. Originality/value The proposed approach implements a new general and flexible strategy for repairing detected inconsistencies in a deferred manner and possibly in multiple steps, according to varying user’s requirements and to specifications which are customary in the real world.

show abstract

A Comparison of Different Forms of Temporal Data Management

Cited by 5 publications

References 9 publications

Temporal Data Management – An Overview

Temporal Data Management – An Overview

A systematic approach to efficiently managing the effects of retroactive updates of time-varying data in multiversion XML databases

Deferred repair of inconsistencies resulting from retroactive updates of temporal XML currency data

Contact Info

Product

Resources

About