The SDCC framework for integrating existing algorithms for diverse data warehouse maintenance tasks

Zhang, Xin; Rundensteiner, Elke A.

doi:10.1109/ideas.1999.787269

Cited by 2 publications

(1 citation statement)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Much of this work focused on object oriented databases (OODB), including the work by Rundensteiner et al [6] [7] and the temporal versioning research by Grandi et al [8] and Galante et al [9]. There were a number of papers by Zaniolo, Moon, Curino, et al on quantifying and supporting schema evolution in RDBMSes [10] [11] [12] [13].…”

Section: Introductionmentioning

confidence: 99%

Storing Long-Lived Concurrent Schema and Data Versions in Relational Databases

Wall

Angryk

2015

Advances in Intelligent Systems and Computing

View full text Add to dashboard Cite

Abstract.Although there is a strong focus on NoSQL databases for cloud computing environments, traditional relational data bases are still an integral part of many computing services in the cloud. Two significant issues in managing a relational database in a cloud environment are handling the inevitable evolution of the database schema and managing changes to system configuration and other data stored in the database as the system evolves over time. Techniques for handling these issues in on-premise databases are much less feasible in cloud computing environments, which demand efficiency, elasticity, and scalability. We propose a versioning system that can be used in relational databases to allow new versions of the database schema and data to be maintained within the same database as the production data. Past research on versioning either handles data versioning but not schema changes, or handles both but is focused on OLAP or XML databases. In this paper, we describe a mechanism for storing concurrent versions of data in an OLTP database. We explore two different implementation alternatives for versioned data storage and evaluate their relative merits given different workloads. We provide a concrete description of how this can be implemented within the InnoDB storage engine, which is the default data store for MySQL databases, and we present a quantitative comparison of the two implementations in InnoDB.

show abstract