Issues of object-relational view design in data warehousing environment

Research output: Journal Publications and Reviews (RGC: 21, 22, 62)21_Publication in refereed journalpeer-review

10 Scopus Citations
View graph of relations

Author(s)

  • Vivekanand Gopalkrishnan
  • Qing Li
  • Kamalakar Karlapalem

Detail(s)

Original languageEnglish
Pages (from-to)2732-2737
Journal / PublicationProceedings of the IEEE International Conference on Systems, Man and Cybernetics
Volume3
Publication statusPublished - 1998
Externally publishedYes

Conference

TitleProceedings of the 1998 IEEE International Conference on Systems, Man, and Cybernetics. Part 3 (of 5)
CitySan Diego, CA, USA
Period11 - 14 October 1998

Abstract

Data Warehouses contain vast amount of data, often from different sources. In order to support complex queries of various decision support systems, we need to store materialized views of data. These views represent integrated data based on complex aggregate queries, and should be available consistently and instantaneously, which would not be possible if those queries had to be invoked each time on the varied data sources. Conventional approaches have been based on the relational model where materialized views are stored as tables in the warehouse. This also means that semantics of the data warehouse structure are hidden. Using Object-oriented methodology, we can explicitly represent the semantics and reuse view (class) definitions based on the ISA hierarchy and the class composition hierarchies, thereby resulting in a more efficient view mechanism. This paper deals with the issues concerned with providing an Object-Relational View (ORV) mechanism for the data warehouse. Primary issues are: providing object views for the relational data and for aggregate/summary data. These include translating the relational data structures into a class hierarchy, defining class structures for the summary views, supporting object ids for object instances of the views (classes) generated, handling those classes with respect to classes in maintenance and providing links to other classes in the hierarchy, and accessing and querying these view classes.