Construction and Maintenance of Heterogeneous Data Warehouses

Construction and Maintenance of Heterogeneous Data Warehouses

M. Badri, F. Boufarès, S. Hamdoun, V. Heiwy, K. Lellahi
DOI: 10.4018/978-1-60566-756-0.ch011
OnDemand:
(Individual Chapters)
Available
$37.50
No Current Special Offers
TOTAL SAVINGS: $37.50

Abstract

The data necessary to decisional ends are increasingly complex. They have heterogeneous formats and come from distributed sources. They can be classified in three categories: the structured data, the semistructured data and unstructured data. In this work, we are interested in the field of data integration with the aim of construction and maintenance of warehouses whose sources are completely heterogeneous and belonging to the various categories. We propose a formal framework based on the definition of an integration environment. A set of “integration relationships” between the components of the sources is thus defined: an equivalence relation and a strict order relation. These relationships are independent of any data sources modelling. These last can be then heterogeneous and having different models and/ or categories. Two different physical architectures, to create and maintain the warehouses and the materialized views, are given.
Chapter Preview
Top

Introduction

Nowadays, the current informational environment is characterized by strongly distributed heterogeneous data. Complex applications such as knowledge extraction, data mining, learning and web applications use heterogeneous and distributed data sources (Boussaïd, Darmont, Bentayeb & Loudcher-Rabaseda, 2008). Thus the need of integrating and manipulating of large amount of data is more and more increasing. In the absence, first, of tools for the heterogeneous data integration, and second, of formalisms for modelling the integration of these data, we propose in this chapter early attempts to formalise the integration of heterogeneous data and their maintenance. Indeed, the data can be classified in three categories: structured (relational and object data), semi-structured (HTML, XML, graphs) and unstructured (text, images, sounds) (see figure 1).

Figure 1.

The heterogeneity of DW’s sources

978-1-60566-756-0.ch011.f01

Our contribution is twofold: the first part of our work concerns the beginning of the Data Warehouse (DW) life cycle: the building of DW from heterogeneous sources and the second part is related to the maintenance phase.

In the literature (Da Silva, Filha, Laender & Embley, 2002; Saccol & Heuser, 2002; Kim & Park, 2003; Beneventano, Bergamaschi, Castano, Antonellis, Ferrara, Guerra, Mandreoli, Ornetti & Vincini, 2002), there is no consensus on the significance of heterogeneity. According to the domain and the type of considered application, the treatment and the interpretation of heterogeneity were made in several ways. Considering this ambiguous interpretation of heterogeneity, we adopt, in our integration work, the definitions below which will enable us to treat all categories together.

Data sources are known as heterogeneous if they check one of the two following properties:

  • 1)

    They belong to the same category of data but they have different modellings;

  • 2)

    They belong to different data categories.

Thus, the integration of a relational database (DB) and of an object-relational one is an example of handling heterogeneous data sources. It is the same case for a relational and an XML DBs.

A DW results from data sources integration. It is a subject-oriented, integrated, time-variant, and non-volatile collection of data in support of management’s decision making process (Inmon, 1995). A heterogeneous DW is a one whose sources are heterogeneous.

Our theoretical approach allows us the integration of various heterogeneous data sources (DS) (Hamdoun, 2006; Hamdoun, Boufarès & Badri, 2007; Badri, 2008). This approach takes as an input an integration environment (see figure 2) as a set of DS and a set of relationships between them and returns a DW. Because it deals with heterogeneous data, our approach proposes an unified formal theoretical representation of them. It is general and applicable for any kind of integration. We will be able for instance to duplicate databases or to create several versions of databases (Hamdoun, 2006; Hamdoun, Boufarès & Badri, 2007; Badri, 2008).

Figure 2.

Example of an integration environment

978-1-60566-756-0.ch011.f02

Complete Chapter List

Search this Book:
Reset