TPC-BiH: A Benchmark for Bitemporal Databases

Abstract

Abstract. An increasing number of applications such as risk evaluation in banking or inventory management require support for temporal data. After more than a decade of standstill, the recent adoption of some bitemporal features in SQL:2011 has reinvigorated the support among commercial database vendors, who incorporate an increasing number of relevant bitemporal features. Naturally, assessing the performance and scalability of temporal data storage and operations is of great concern for potential users. The cost of keeping and querying history with novel operations (such as time travel, temporal joins or temporal aggregations) is not adequately reflected in any existing benchmark. In this paper, we present a benchmark proposal which provides comprehensive coverage of the bitemporal data management. It builds on the solid foundations of TPC-H but extends it with a rich set of queries and update scenarios. This workload stems both from real-life temporal applications from SAP's customer base and a systematic coverage of temporal operators proposed in the academic literature. We present preliminary results of our benchmark on a number of temporal database systems, also highlighting the need for certain language extensions.

Understanding business trends from data evolution with Tornado

“…We plan to conduct experiments of Tornado with the TCPBiH benchmark [15], which is a bi-temporal extension of the TPC-H benchmark. We are also working on multi-query optimization techniques, and also incremental pre-computation mechanism introduced in [16].…”

Storing and processing temporal data in a main memory column store

“…For the evaluation of the memory layouts we use a data generator based on TPC-H with additional update scenarios to create a realistic workload containing a history of data as described in [6].…”

“…Furthermore, it simplifies the development of new benchmarks. We use this system to micro-benchmark different implementations of temporal operators and for the development of new benchmarks such as [6].…”

A Diy Approach to Uni-Temporal Database Implementation

“…Approaching such a problem and its related, a study of temporal DBMS has been developed for decades [1]. Despite lots of research on tDBMS, practical tDBMS products are rare, and even more, most of them are in fact an extension of traditional RDBMS [11], in general developing a tDBMS application is still a tough and often individualized task for a MIS (Management Information System) developer team.…”

“…Following these guidelines, towards a generic design scheme for tDBMSrelated MIS applications we focus on the transaction-time property of data (so we call this approach as of the unitemporal database implementation) and treat it as a common attribute [9], this is contrasted with the nowadays so-called "bitemporal database" [11], i.e., a general temporal database.…”