The Data warehouse is not an autonomous data store, because it depends upon its operational source(s) for data population. Due to changes in real-world scenarios, operational sources may evolve, but the conventional data warehouse is not developed to handle the modifications in evolved operational sources. Therefore, instance and schema changes in operational sources cannot be adapted in the conventional data warehouse without loss of information. Multiversion data warehouses are proposed as an alternative to handle these problems of evolution. In this chapter we discuss and illustrate how versioning is implemented and how it can be used in practical data warehouse lifecycle. It is designed as a tutorial for users to collect and understand the concepts behind a versioning solution. Therefore, the purpose of this chapter is to collect and integrate the concepts, issues and solutions of multiversion data warehouses in a tutorial-like approach, to provide a unified source for users that need to understand version functionality and mechanisms.
[1]
Robert Wrembel,et al.
Formal approach to modelling a multiversion data warehouse
,
2006
.
[2]
Surajit Chaudhuri,et al.
An overview of data warehousing and OLAP technology
,
1997,
SGMD.
[3]
Elke A. Rundensteiner,et al.
Maintaining data warehouses over changing information sources
,
2000,
CACM.
[4]
. J.A.Nasir,et al.
Transparent Querying Multiple-versions of Data Warehouse
,
2006
.
[5]
Gottfried Vossen,et al.
Schema versioning in data warehouses: Enabling cross-version querying via schema augmentation
,
2006,
Data Knowl. Eng..
[6]
Hiroaki Kitano,et al.
A graphical notation for biochemical networks
,
2003
.
[7]
Stephen R. Gardner.
Building the data warehouse
,
1998,
CACM.