Encyclopedia of Data Warehousing and Mining
|
|
- Melvyn Mason
- 2 years ago
- Views:
Transcription
1 Encyclopedia of Data Warehousing and Mining Second Edition John Wang Montclair State University, USA Volume IV Pro-Z Information Science reference Hershey New York
2 Director of Editorial Content: Director of Production: Managing Editor: Assistant Managing Editor: Typesetter: Cover Design: Printed at: Kristin Klinger Jennifer Neidig Jamie Snavely Carole Coulson Amanda Appicello, Jeff Ash, Mike Brehem, Carole Coulson, Elizabeth Duke, Jen Henderson, Chris Hrobak, Jennifer Neidig, Jamie Snavely, Sean Woznicki Lisa Tosheff Yurchak Printing Inc. Published in the United States of America by Information Science Reference (an imprint of IGI Global) 701 E. Chocolate Avenue, Suite 200 Hershey PA Tel: Fax: Web site: and in the United Kingdom by Information Science Reference (an imprint of IGI Global) 3 Henrietta Street Covent Garden London WC2E 8LU Tel: Fax: Web site: Copyright 2009 by IGI Global. All rights reserved. No part of this publication may be reproduced, stored or distributed in any form or by any means, electronic or mechanical, including photocopying, without written permission from the publisher. Product or company names used in this set are for identification purposes only. Inclusion of the names of the products or companies does not indicate a claim of ownership by IGI Global of the trademark or registered trademark. Library of Congress Cataloging-in-Publication Data Encyclopedia of data warehousing and mining / John Wang, editor. -- 2nd ed. p. cm. Includes bibliographical references and index. Summary: "This set offers thorough examination of the issues of importance in the rapidly changing field of data warehousing and mining"--provided by publisher. ISBN (hardcover) -- ISBN (ebook) 1. Data mining. 2. Data warehousing. I. Wang, John, QA76.9.D37E dc British Cataloguing in Publication Data A Cataloguing in Publication record for this book is available from the British Library. All work contributed to this encyclopedia set is new, previously-unpublished material. The views expressed in this encyclopedia set are those of the authors, but not necessarily of the publisher. If a library purchased a print copy of this publication, please go to for information on activating the library's complimentary electronic access to this publication.
3 Section: Time Series 1929 Temporal Extension for a Conceptual Multidimensional Model T Elzbieta Malinowski Universidad de Costa Rica, Costa Rica Esteban Zimányi Université Libre de Bruxelles, Belgium INTRODUCTION Data warehouses integrate data from different source systems to support the decision process of users at different management levels. Data warehouses rely on a multidimensional view of data usually represented as relational tables with structures called star or snowflake schemas. These consist of fact tables, which link to other relations called dimension tables. A fact table represents the focus of analysis (e.g., analysis of sales) and typically includes attributes called measures. Measures are usually numeric values (e.g., quantity) used for performing quantitative evaluation of different aspects in an organization. Measures can be analyzed according to different analysis criteria or dimensions (e.g., store dimension). Dimensions may include hierarchies (e.g., month-year in the time dimension) for analyzing measures at different levels of detail. This analysis can be done using on-line analytical processing (OLAP) systems, which allow dynamic data manipulations and aggregations. For example, the roll-up operation transforms detailed measures into aggregated data (e.g., daily into monthly or yearly sales) while the drill-down operations does the contrary. Multidimensional models include a time dimension indicating the timeframe for measures, e.g., 100 units of a product were sold in March However, the time dimension cannot be used to keep track of changes in other dimensions, e.g., when a product changes its ingredients. In many cases the changes of dimension data and the time when they have occurred are important for analysis purposes. Kimball and Ross (2002) proposed several implementation solutions for this problem in the context of relational databases, the so-called slowly-changing dimensions. Nevertheless, these solutions are not satisfactory since either they do not preserve the entire history of data or are difficult to implement. Further, they do not consider the research realized in the field of temporal databases. Temporal databases are databases that support some aspects of time (Jensen & Snodgrass, 2000). This support is provided by means of different temporality types 1, to which we refer in the next section. However, even though temporal databases allow to represent and to manage time-varying information, they do not provide facilities for supporting decision-making process when aggregations of high volumes of historical data are required. Therefore, a new field called temporal data warehouses joins the research achievements of temporal databases and data warehouses in order to manage time-varying multidimensional data. BACKGROUND Temporal support in data warehouses is based on the different temporality types used in temporal databases. Valid time () specifies the time when data is true in the modeled reality, e.g., the time when a specific salary was paid for an employee. Valid time is typically provided by users. Transaction time (TT) indicates the time when data is current in the database and may be retrieved. It is generated by the database management system (DBMS). Both temporality types, i.e., valid time and transaction time, can be combined defining bitemporal time (BT). Finally, changes in time defined for an object as a whole define the lifespan () of an object, e.g., the time when an employee was working for a company. One characteristic of temporality types is their precision or granularity, indicating the duration of the time units that are relevant for an application. For example, the valid time associated to an employee s salary may be of granularity month. On the other hand, transaction time being system defined is typically of a millisecond granularity. There is still lack of an analysis determining which temporal support is important for data warehouse ap- Copyright 2009, IGI Global, distributing in print or electronic forms without written permission of IGI Global is prohibited.
4 Temporal Extenstion for a Conceptual Multidimensional Model plications. Most works consider valid time (e.g., Body, Miquel, Bédard, & Tchounikine, 2003; Wrembel & Bebel, 2007; Mendelzon & Vaisman, 2003). To our knowledge, no work includes lifespan support in temporal data warehouses. However, lifespan is important since it can help to discover, e.g., how the exclusion of some products influences sales. On the other hand, very few works relate to transaction time. For example, Martín and Abelló (2003) transform transaction time from source systems to represent valid time. This approach is semantically incorrect because data may be included in databases after their period of validity has expired. Further, transaction time coming from source system plays an important role in temporal data warehouses when traceability is required, e.g., for fraud detection. Other authors consider transaction time generated in temporal data warehouses in the same way as transaction time in temporal databases (e.g., Martín & Abelló, 2003; Mendelzon & Vaisman, 2003; Ravat & Teste, 2006). However, since data in temporal data warehouses is neither modified nor deleted, transaction time in a data warehouse represents the time when data was loaded into a data warehouse. Therefore, we propose to call it loading time (LT) (Malinowski & Zimányi, 2006a). LT can differ from transaction time or valid time of source systems due to the delay between the time when the changes have occurred in source systems and the time when these changes are integrated into a temporal data warehouse. Another approach (Brucker & Tjoa, 2002) considers valid time, transaction time, and loading time. However, they limit the usefulness of these temporality types for only active data warehouses, i.e., for data warehouses that include event-conditionaction rules (or triggers). The inclusion of temporal support raise many issues, such as efficient temporal aggregation of multidimensional data (Moon, Vega, & Immanuel, 2003), correct aggregation in presence of data and schema changes (Body et al., 2003; Eder, Koncilia, & Morzy, 2002; Wrembel & Bebel, 2007; Mendelzon & Vaisman, 2003; Golfarelli, Lechtenbörger, Rizzi, & Vossen, 2006), or temporal view materialization from non-temporal sources (Yang & Widom, 1998). Even though the works related to schema and data changes define models for temporal data warehouses, what is still missing is a conceptual model that allows decision-making Figure 1. An example of a multidimensional schema for a temporal data warehouse Category Category name Responsible Max. amount Product groups Product Product number Name Size Distributor Sales district District name Representative Contact info District area No employees Client Client id First name Last name Birth date Profession Salary range Sales Quantity Amount Sales organization Store Store number Name Manager s name Area 1930
5 Temporal Extension for a Conceptual Multidimensional Model users to represent data requirement for temporal data warehouses. This model should allow specifying multidimensional elements, i.e., dimensions, hierarchies, facts, and measures, and allow users to clearly indicate which elements they want to be time invariant and for which the changes in time should be kept. MAIN FOCUS In this section we present the MultiDim model, a conceptual multidimensional model (Malinowski & Zimányi, 2008a) 2 extended with temporal support (Malinowski & Zimányi, 2006a, 2006b). This model allows users and designers to represent at the conceptual level all elements required in temporal data warehouse applications. Multidimensional Model for Temporal Data warehouses The MultiDim model supports different temporality types: lifespan (), valid time (), transaction time (TT), and bitemporal time (BT) coming from source systems (if available) and additionally, loading time (LT) generated in a data warehouse. To describe our model we use the example shown in Figure 1. It includes a set of levels organized into dimensions and a fact relationship. A level corresponds to an entity type in the entity-relationship model and represents a set of instances called members that have common characteristics. For example, Product, Category, and Store are some of the levels in Figure 1. Levels contain one or several key attributes (underlined in Figure 1), identifying uniquely the members of a level, and may also have other descriptive attributes. A temporal level is a level for which the application needs to keep the lifespan of its members (e.g., inserting or deleting a product). A temporal attribute is an attribute that keeps the changes in its value (e.g., changing a product s size) and the time when they occur. For example, the Product level in Figure 1 is a temporal level that includes temporal attributes Size and Distributor. A fact relationship expresses the focus of analysis and represents an n-ary relationship between levels. For example, the Sales fact relationship between the Product, Store, and Client levels in Figure 1 is used for analyzing sales in different stores. A fact relationship may contain attributes commonly called measures. They contain data (usually numerical) that are analyzed using the different dimensions. For example, the Sales fact relationship in Figure 1 includes the measures Quantity and Amount. In the MultiDim model measures are temporal, i.e., they always require a temporality type (, TT, BT, and/or LT). A dimension allows to group data that shares a common semantic meaning within the domain being modeled, e.g., all data related to a product. It is composed of either a level or one or more hierarchies. For example, Client in Figure 1 is a one-level dimension. Hierarchies are required for allowing users to analyze data at different levels of detail. A hierarchy contains several related levels, e.g., Product and Category in Figure 1. Given two related levels of a hierarchy, one of them is called child and the other parent depending on whether they include more detailed or more general data, respectively. In Figure 1, the Product level is a child level while the Category level is a parent level. Key attributes of a parent level define how child members are grouped for the roll-up operation. For example, in Figure 2 since Category name is the key of the Category level, products will be grouped according to the category to which they belong. The relationships composing the hierarchies are called child-parent relationships. These relationships are characterized by cardinalities that indicate the minimum and the maximum number of members in one level that can be related to a member in another level. Child-parent relationships may include temporal support. For example, in Figure 1 the symbol between Product and Category indicates that the evolution on time of assignments of products to categories will be kept. Temporal support for relationships leads to two interpretations of cardinalities. The snapshot cardinality is valid at every time instant whereas the lifespan cardinality is valid over the entire member s lifespan. The former cardinality is represented using the symbol indicating temporality type next to the link between levels while the lifespan cardinality includes the symbol surrounded by a circle. In Figure 1, the snapshot cardinality between Product and Category levels is many-to-one while the lifespan cardinality is many-to-many. They indicate that a product belongs to only one category at every time instant but belongs to many categories over its lifespan, i.e., its assignment to categories may change. The relationship between levels may include different temporality types:, TT, combination of both, and/or LT T
6 Temporal Extenstion for a Conceptual Multidimensional Model Figure 2. Examples of temporal hierarchies: a) nontemporal relationship between a temporal and a nontemporal levels, and b) temporal relationship between non-temporal levels Employee Employee id Employee name Position Work (a) (b) Since hierarchies in a dimension may express different conceptual structures used for analysis purposes, we use a criterion name to differentiate them, such as Product groups or Sales organization in Figure 1. Modeling Temporal Aspects Our model supports temporality in an orthogonal way, i.e., hierarchies may contain temporal or non-temporal levels associated with temporal or non-temporal links. Similarly, temporal or non-temporal levels may have temporal or non-temporal attributes. This approach differs from the one used in many temporal models. We consider that it is important to allow users to choose which elements should be temporal or not. For example, Figure 2 (a) represents a hierarchy composed by a temporal level (Product) and a non-temporal level (Category) with a temporal attribute associated with a non-temporal link. Therefore, the lifespan of products as well as the changes of responsible and maximum amount of categories are kept; on the other hand, other attributes of the levels either do not change or only the last modification is kept. The example in Figure 2 (b) shows a hierarchy with two non-temporal levels associated with a temporal link. This keeps track Section Section name Activity of the evolution of relationships between employees and sections but we do not store the changes in levels, e.g., when an employee changes its position. However, to ensure correct management of hierarchies in temporal data warehouses and avoid dangling references, i.e., references to non-existing elements, several constraints should be ensured (Malinowski & Zimányi, 2006a). Another characteristic of our model is that it uses a consistent approach for providing temporal support for the different elements of a multi-dimensional model, i.e., for levels, hierarchies, and measures. Our model avoids mixing two different approaches where dimensions include explicit temporal support while measures require the presence of the traditional time dimension for keeping track of changes. Since measures are attributes of fact relationships, we provide temporal support for them in the same way as it is done for levels attributes. An important question is thus whether it is necessary to have a time dimension in the schema when including temporality types for measures. If all attributes of the time dimension can be obtained by applying time manipulation functions, such as the corresponding week, month, or quarter, this dimension is not required anymore. However, in some temporal data warehouse applications this calculation can be very time-consuming, or the time dimension contains data that cannot be derived, e.g., events such as promotional seasons. Thus, the time dimension is included in a schema depending on users requirements and the capabilities provided by the underlying DBMS. Another aspect is the inclusion of different temporality types for measures. The usual practice in temporal data warehouses is to associate valid time support with measures. However, different temporal support can be available in source systems. In Malinowski and Zimányi (2006b), we present several real-world scenarios that include different temporality types for measures enriching the analysis spectrum. The examples in Figure 3 show simplified schemas that include, respectively, loading time and transaction time for measures. The former is used when users require the history of how source data has evolved, but sources are either non-temporal or temporal support is implemented in an ad-hoc manner that can be both inefficient and difficult to automate (Yang & Widom, 1998). The schema in Figure 3 b) is used for an insurance company having as analysis focus the amount of insurance payments. Such a schema 1932
7 Temporal Extension for a Conceptual Multidimensional Model Figure 3. Examples of schemas with a) LT and b) TT support for measures Product Product number Product name Size Product groups Category Category name T Supplier Supplier id Supplier name LT Inventory Q uantity Cost Warehouse WH number WH name City name State name (a) Insurance type Type id Insurance name Category Client Client id Client name Insurance object Object id Object name TT Fraud detection Amount (b) Insurance agency Agency id could be used, e.g., to track internal frauds that modify the amount of insurance paid to clients, since the time when the measure values change is kept. In Malinowski and Zimányi (2006b) we discuss several problems that may occur when data from source systems is aggregated before being loaded into temporal data warehouses. These include different time granularities between source systems and a data warehouse, measure aggregations with different time granularities, and temporal support for aggregated measures. FUTURE TRENDS An important issue in temporal data warehouses is the aggregation in the presence of changes in dimension data, schema, or both. Different solutions have already been proposed (e.g., Eder et al., 2002; Mendelzon & Vaisman, 2003; Wrembel & Bebel, 2007; Body et al., 2003). Nevertheless, these proposals require specific software and query languages for implementing and manipulating multidimensional data that vary over time. Further, they do not consider different aspects as mentioned in this paper, e.g., different temporal support in hierarchies and measures. Another issue is the implementation of temporal data warehouses in current DBMSs, which do not yet provide temporal support. To our knowledge, there are very few proposals for implementing temporal data warehouses in current DBMSs (e.g., Martín & Abelló, 2003; Malinowski & Zimányi, 2006c; Ravat et al., 1999; Mendelzon & Vaisman, 2003). However, only the latter authors provide manipulation features for the proposed structures. 1933
8 Temporal Extenstion for a Conceptual Multidimensional Model CONCLUSION Combining the two research areas of data warehouses and temporal databases, allows one to combine the achievements of each of them leading to the emerging field of temporal data warehouses. The latter raises several research issues, such as the inclusion of different temporal support, conceptual modeling, and measure aggregations, among others. In this paper, we first proposed the inclusion of four different temporality types: three of them come from source systems (if they are available), i.e., valid time, transaction time (or combination of both), and lifespan. A new temporality type, called loading time, is generated in temporal data warehouses. It indicates when data was stored in a temporal data warehouse. We also presented a conceptual model that is able to express users requirements for time-varying multidimensional data. The MultiDim model allows temporal support for levels, attributes, relationships between levels forming a hierarchy, and measures. For temporal hierarchies and measures, we discussed different issues that are relevant to ensure the correct data management in temporal data warehouses. The inclusion of temporality types in a conceptual model allows users, designers, and implementers to include temporal semantics as an integral part of temporal data warehouses. In this way, temporal extensions offer more symmetry to multidimensional models representing in a symmetric manner changes and the time when they occur for all elements of a data warehouse. Since conceptual models are platform independent, logical and physical models can be derived from such a conceptual representation. REFERENCES Body, M., Miquel, M., Bédard, Y., & Tchounikine, A. (2003). Handling Evolution in Multidimensional Structures. Proceedings of the 19 th International Conference on Data Engineering, pp IEEE Computer Society Press. Bruckner, R. & Tjoa, A. (2002). Capturing Delays and Valid Times in Data Warehouses: Towards Timely Consistent Analyses, Journal of Intelligent Information Systems, 19(2), pp Eder, J., Koncilia, Ch., & Morzy, T. (2002). The COMET Metamodel for Temporal Data Warehouses. Proceedings of the 14 th International Conference on Advanced Information Systems Engineering, pp Lecture Notes in Computer Science, N Springer. Golfarelli, M., Lechtenbörger, J., Rizzi, S., & Vossen, V. (2006). Schema Versioning in Data Warehouses: Enabling Cross-Version Querying Via Schema Augmentation. Data & Knowledge Engineering, 59(2), pp Jensen, C.S. & Snodgrass, R. (2000). Temporally Enhanced Database Design. In M. Papazoglou, S. Spaccapietra, & Z. Tari (Eds.), Advances in Object-Oriented Data Modeling, pp Cambridge, MIT Press. Kimball, R., & Ross, M. (2002). The Data Warehouse Toolkit. John Wiley & Sons Publishers. Malinowski, E. & Zimányi, E. (2008a). Multidimensional Conceptual Models, in this book. Malinowski, E. & Zimányi, E. (2008b). Advanced Data Warehouse Design: From Conventional to Spatial and Temporal Applications. Springer. Malinowski, E. & Zimányi, E. (2006a). A Conceptual Solution for Representing Time in Data Warehouse Dimensions. Proceedings of the 3 rd Asia-Pacific Conference on Conceptual Modelling, pp Australian Computer Society. Malinowski, E. & Zimányi, E. (2006b). Inclusion of Time-Varying Measures in Temporal Data Warehouses. Proceedings of the 8 th International Conference on Enterprise Information Systems, pp Malinowski, E. & Zimányi, E. (2006c). Object-Relational Representation of a Conceptual Model for Temporal Data Warehouses. Proceedings of the 18 th International Conference on Advanced Information Systems Engineering, pp Lecture Notes in Computer Science, N Springer. Martín, C. & Abelló, A. (2003). A Temporal Study of Data Sources to Load a Corporate Data Warehouse. Proceedings of the 5 th International Conference on Data Warehousing and Knowledge Discovery, pp Lecture Notes in Computer Science, N Springer. Mendelzon, A. & Vaisman, A. (2003). Time in Multidimensional Databases. In M. Rafanelli (Ed.), Multi- 1934
9 Temporal Extension for a Conceptual Multidimensional Model dimensional Databases: Problems and Solutions, pp Idea Group Publishing. Moon, B., Vega, F., & Immanuel, V. (2003). Efficient Algorithms for Large-Scale Temporal Aggregation. IEEE Transactions on Knowledge and Data Engineering, 15(3), pp Ravat, F. & Teste, F. (2006). Supporting Changes in Multidimensional Data Warehouses. International Review of Computer and Software, 1(3), pp Wrembel, T. & Bebel, B.(2007). Metadata Management in a Multiversion Data Warehouse. In S. Spaccapietra (Ed.), Journal on Data Semantics, VIII, pp Lecture Notes in Computer Science, N Springer Yang, J. & Widom, J. (1998). Maintaining Temporal Views Over Non-Temporal Information Source for Data Warehousing. Proceedings of the 6 th International Conference on Extending Database Technology, pp Lecture Notes in Computer Science, N Springer. KEY TERMS Bitemporal: A combination of both transaction and valid time. Conceptual Model: A model for representing schemas that are designed to be as close as possible to users perception, not taking into account any implementation considerations. Loading Time: A temporal specification that keeps the information when a data element is stored in a data warehouse. Granularity: A partitioning of a domain in groups of elements where each group is perceived as an indivisible unit (a granule) at a particular abstraction level. Lifespan: The record of the evolution of the membership of an instance into its type. Multidimensional Model: A model for representing the information requirements of analytical applications. A multidimensional model comprises facts, measures, dimensions, and hierarchies. Temporality Types: Different temporal support that can be provided by a system. They include transaction time, valid time, lifespan, and loading time. Transaction Time: A temporal specification that keeps the information on when a data element is stored in and deleted from the database. Valid Time: A temporal specification that keeps information on when a data element stored in the database is considered valid in the perceived reality from the application viewpoint. ENDNOTES 1 They are usually called time dimensions; however, we use the term dimension in the multidimensional context. 2 We only include some elements of the MultiDim model in order to focus on its temporal extension. T 1935
Encyclopedia of Distance Learning Second Edition
Encyclopedia of Distance Learning Second Edition Patricia Rogers Bemidji State, USA Gary Berg Chapman University, USA Judith Boettcher Designing for Learning, USA Carole Howard Touro University International,
DIMENSION HIERARCHIES UPDATES IN DATA WAREHOUSES A User-driven Approach
DIMENSION HIERARCHIES UPDATES IN DATA WAREHOUSES A User-driven Approach Cécile Favre, Fadila Bentayeb, Omar Boussaid ERIC Laboratory, University of Lyon, 5 av. Pierre Mendès-France, 69676 Bron Cedex, France
IMPLEMENTING SPATIAL DATA WAREHOUSE HIERARCHIES IN OBJECT-RELATIONAL DBMSs
IMPLEMENTING SPATIAL DATA WAREHOUSE HIERARCHIES IN OBJECT-RELATIONAL DBMSs Elzbieta Malinowski and Esteban Zimányi Computer & Decision Engineering Department, Université Libre de Bruxelles 50 av.f.d.roosevelt,
Advanced Data Warehouse Design
Data-Centric Systems and Applications Advanced Data Warehouse Design From Conventional to Spatial and Temporal Applications Bearbeitet von Elzbieta Malinowski, Esteban Zimányi 1st ed. 2008. Corr. 2nd printing
A Survey on Bitemporal Data Warehousing System and Data Warehouse Design Techniques.
A Survey on Bitemporal Data Warehousing System and Data Warehouse Design Techniques. P.N.V.S.Pavan Kumar, K.Bala Chowdappa, S.Subba Lakshmi CSE Department, G.Pulla Reddy Engineering College(Autonomous)
2 Associating Facts with Time
TEMPORAL DATABASES Richard Thomas Snodgrass A temporal database (see Temporal Database) contains time-varying data. Time is an important aspect of all real-world phenomena. Events occur at specific points
Alejandro Vaisman Esteban Zimanyi. Data. Warehouse. Systems. Design and Implementation. ^ Springer
Alejandro Vaisman Esteban Zimanyi Data Warehouse Systems Design and Implementation ^ Springer Contents Part I Fundamental Concepts 1 Introduction 3 1.1 A Historical Overview of Data Warehousing 4 1.2 Spatial
Data warehouses. Data Mining. Abraham Otero. Data Mining. Agenda
Data warehouses 1/36 Agenda Why do I need a data warehouse? ETL systems Real-Time Data Warehousing Open problems 2/36 1 Why do I need a data warehouse? Why do I need a data warehouse? Maybe you do not
A Design and implementation of a data warehouse for research administration universities
A Design and implementation of a data warehouse for research administration universities André Flory 1, Pierre Soupirot 2, and Anne Tchounikine 3 1 CRI : Centre de Ressources Informatiques INSA de Lyon
My Favorite Issues in Data Warehouse Modeling
University of Münster My Favorite Issues in Data Warehouse Modeling Jens Lechtenbörger University of Münster & ERCIS, Germany http://dbms.uni-muenster.de Context Data Warehouse (DW) modeling ETL design
Dimensional Modeling for Data Warehouse
Modeling for Data Warehouse Umashanker Sharma, Anjana Gosain GGS, Indraprastha University, Delhi Abstract Many surveys indicate that a significant percentage of DWs fail to meet business objectives or
Methodology Framework for Analysis and Design of Business Intelligence Systems
Applied Mathematical Sciences, Vol. 7, 2013, no. 31, 1523-1528 HIKARI Ltd, www.m-hikari.com Methodology Framework for Analysis and Design of Business Intelligence Systems Martin Závodný Department of Information
Investigating the Effects of Spatial Data Redundancy in Query Performance over Geographical Data Warehouses
Investigating the Effects of Spatial Data Redundancy in Query Performance over Geographical Data Warehouses Thiago Luís Lopes Siqueira Ricardo Rodrigues Ciferri Valéria Cesário Times Cristina Dutra de
INTEROPERABILITY IN DATA WAREHOUSES
INTEROPERABILITY IN DATA WAREHOUSES Riccardo Torlone Roma Tre University http://torlone.dia.uniroma3.it/ SYNONYMS Data warehouse integration DEFINITION The term refers to the ability of combining the content
6NF CONCEPTUAL MODELS AND DATA WAREHOUSING 2.0
ABSTRACT 6NF CONCEPTUAL MODELS AND DATA WAREHOUSING 2.0 Curtis Knowles Georgia Southern University ck01693@georgiasouthern.edu Sixth Normal Form (6NF) is a term used in relational database theory by Christopher
Copyright 2007 Ramez Elmasri and Shamkant B. Navathe. Slide 29-1
Slide 29-1 Chapter 29 Overview of Data Warehousing and OLAP Chapter 29 Outline Purpose of Data Warehousing Introduction, Definitions, and Terminology Comparison with Traditional Databases Characteristics
Foundations of Business Intelligence: Databases and Information Management
Chapter 6 Foundations of Business Intelligence: Databases and Information Management 6.1 2010 by Prentice Hall LEARNING OBJECTIVES Describe how the problems of managing data resources in a traditional
Designing an Object Relational Data Warehousing System: Project ORDAWA * (Extended Abstract)
Designing an Object Relational Data Warehousing System: Project ORDAWA * (Extended Abstract) Johann Eder 1, Heinz Frank 1, Tadeusz Morzy 2, Robert Wrembel 2, Maciej Zakrzewicz 2 1 Institut für Informatik
Analysis Framework for Reduced Data Warehouse
Analysis Framework for Reduced Data Warehouse Authors : Franck Ravat, Jiefu Song, Olivier Teste Team SIG, IRIT, Toulouse. EDA-2015 Brussels, Belgium 02/04/2015 Plan 1. Context 2. Multi-states analyses
Data warehouse design
DataBase and Data Mining Group of DataBase and Data Mining Group of DataBase and Data Mining Group of Database and data mining group, Data warehouse design DATA WAREHOUSE: DESIGN - 1 Risk factors Database
Foundations of Business Intelligence: Databases and Information Management
Foundations of Business Intelligence: Databases and Information Management Content Problems of managing data resources in a traditional file environment Capabilities and value of a database management
Dimensional Modeling and E-R Modeling In. Joseph M. Firestone, Ph.D. White Paper No. Eight. June 22, 1998
1 of 9 5/24/02 3:47 PM Dimensional Modeling and E-R Modeling In The Data Warehouse By Joseph M. Firestone, Ph.D. White Paper No. Eight June 22, 1998 Introduction Dimensional Modeling (DM) is a favorite
5.5 Copyright 2011 Pearson Education, Inc. publishing as Prentice Hall. Figure 5-2
Class Announcements TIM 50 - Business Information Systems Lecture 15 Database Assignment 2 posted Due Tuesday 5/26 UC Santa Cruz May 19, 2015 Database: Collection of related files containing records on
Data Warehousing Systems: Foundations and Architectures
Data Warehousing Systems: Foundations and Architectures Il-Yeol Song Drexel University, http://www.ischool.drexel.edu/faculty/song/ SYNONYMS None DEFINITION A data warehouse (DW) is an integrated repository
Encyclopedia of Information Ethics and Security
Encyclopedia of Information Ethics and Security Marian Quigley Monash University, Australia InformatIon ScIence reference Hershey New York Acquisitions Editor: Development Editor: Senior Managing Editor:
Data Warehousing and Mining: Concepts, Methodologies, Tools, and Applications
Data Warehousing and Mining: Concepts, Methodologies, Tools, and Applications John Wang Montclair State University, USA Information Science reference Hershey New York Acquisitions Editor: Development Editor:
Chapter 6 FOUNDATIONS OF BUSINESS INTELLIGENCE: DATABASES AND INFORMATION MANAGEMENT Learning Objectives
Chapter 6 FOUNDATIONS OF BUSINESS INTELLIGENCE: DATABASES AND INFORMATION MANAGEMENT Learning Objectives Describe how the problems of managing data resources in a traditional file environment are solved
Course 103402 MIS. Foundations of Business Intelligence
Oman College of Management and Technology Course 103402 MIS Topic 5 Foundations of Business Intelligence CS/MIS Department Organizing Data in a Traditional File Environment File organization concepts Database:
Data Warehouse Design
Data Warehouse Design Modern Principles and Methodologies Matteo Golfarelli Stefano Rizzi Translated by Claudio Pagliarani Mc Grauu Hill New York Chicago San Francisco Lisbon London Madrid Mexico City
The Benefits of Data Modeling in Business Intelligence
WHITE PAPER: THE BENEFITS OF DATA MODELING IN BUSINESS INTELLIGENCE The Benefits of Data Modeling in Business Intelligence DECEMBER 2008 Table of Contents Executive Summary 1 SECTION 1 2 Introduction 2
The Benefits of Data Modeling in Data Warehousing
WHITE PAPER: THE BENEFITS OF DATA MODELING IN DATA WAREHOUSING The Benefits of Data Modeling in Data Warehousing NOVEMBER 2008 Table of Contents Executive Summary 1 SECTION 1 2 Introduction 2 SECTION 2
Data warehouse life-cycle and design
SYNONYMS Data Warehouse design methodology Data warehouse life-cycle and design Matteo Golfarelli DEIS University of Bologna Via Sacchi, 3 Cesena Italy matteo.golfarelli@unibo.it DEFINITION The term data
Integrations of Data Warehousing, Data Mining and Database Technologies:
Integrations of Data Warehousing, Data Mining and Database Technologies: Innovative Approaches David Taniar Monash University, Australia Li Chen LaTrobe University, Australia Senior Editorial Director:
THE OPEN UNIVERSITY OF TANZANIA FACULTY OF SCIENCE TECHNOLOGY AND ENVIRONMENTAL STUDIES BACHELOR OF SIENCE IN DATA MANAGEMENT
THE OPEN UNIVERSITY OF TANZANIA FACULTY OF SCIENCE TECHNOLOGY AND ENVIRONMENTAL STUDIES BACHELOR OF SIENCE IN DATA MANAGEMENT ODM 106.DATABASE CONCEPTS COURSE OUTLINE 1.0 Introduction This introductory
Mario Guarracino. Data warehousing
Data warehousing Introduction Since the mid-nineties, it became clear that the databases for analysis and business intelligence need to be separate from operational. In this lecture we will review the
Lecture Data Warehouse Systems
Lecture Data Warehouse Systems Eva Zangerle SS 2013 PART A: Architecture Chapter 1: Motivation and Definitions Motivation Goal: to build an operational general view on a company to support decisions in
Transformation of OWL Ontology Sources into Data Warehouse
Transformation of OWL Ontology Sources into Data Warehouse M. Gulić Faculty of Maritime Studies, Rijeka, Croatia marko.gulic@pfri.hr Abstract - The Semantic Web, as the extension of the traditional Web,
Foundations of Business Intelligence: Databases and Information Management
Foundations of Business Intelligence: Databases and Information Management Problem: HP s numerous systems unable to deliver the information needed for a complete picture of business operations, lack of
Data Warehouse: Introduction
Base and Mining Group of Base and Mining Group of Base and Mining Group of Base and Mining Group of Base and Mining Group of Base and Mining Group of Base and Mining Group of base and data mining group,
Encyclopedia of Data Warehousing and Mining
Encyclopedia of Data Warehousing and Mining Second Edition John Wang Montclair State University, USA Volume III K-Pri Information Science reference Hershey New York Director of Editorial Content: Director
The Benefits of Data Modeling in Business Intelligence
WHITE PAPER: THE BENEFITS OF DATA MODELING IN BUSINESS INTELLIGENCE The Benefits of Data Modeling in Business Intelligence DECEMBER 2008 Table of Contents Executive Summary 1 SECTION 1 2 Introduction 2
Data Warehousing. Overview, Terminology, and Research Issues. Joachim Hammer. Joachim Hammer
Data Warehousing Overview, Terminology, and Research Issues 1 Heterogeneous Database Integration Integration System World Wide Web Digital Libraries Scientific Databases Personal Databases Collects and
Fundamentals of Database Systems, 4 th Edition By Ramez Elmasri and Shamkant Navathe. Table of Contents. A. Short Table of Contents
Fundamentals of Database Systems, 4 th Edition By Ramez Elmasri and Shamkant Navathe Table of Contents A. Short Table of Contents (This Includes part and chapter titles only) PART 1: INTRODUCTION AND CONCEPTUAL
BUILDING OLAP TOOLS OVER LARGE DATABASES
BUILDING OLAP TOOLS OVER LARGE DATABASES Rui Oliveira, Jorge Bernardino ISEC Instituto Superior de Engenharia de Coimbra, Polytechnic Institute of Coimbra Quinta da Nora, Rua Pedro Nunes, P-3030-199 Coimbra,
ISSN: 2319-5967 ISO 9001:2008 Certified International Journal of Engineering Science and Innovative Technology (IJESIT) Volume 2, Issue 4, July 2013
An Architecture for Creation of Multimedia Data Warehouse 1 Meenakshi Srivastava, 2 Dr. S.K.Singh, 3 Dr. S.Q.Abbas 1 Assistant Professor, Amity University,Lucknow Campus, India, 2 Professor, Amity University
Designing a Dimensional Model
Designing a Dimensional Model Erik Veerman Atlanta MDF member SQL Server MVP, Microsoft MCT Mentor, Solid Quality Learning Definitions Data Warehousing A subject-oriented, integrated, time-variant, and
Mobility Data Management
Mobility Data Management (Spatio-Temporal Data Warehouses) Esteban ZIMÁNYI Department of Computer & Decision Engineering (CoDe) Université Libre de Bruxelles ezimanyi@ulb.ac.be CIKM Tutorial on Mobility
Fluency With Information Technology CSE100/IMT100
Fluency With Information Technology CSE100/IMT100 ),7 Larry Snyder & Mel Oyler, Instructors Ariel Kemp, Isaac Kunen, Gerome Miklau & Sean Squires, Teaching Assistants University of Washington, Autumn 1999
Towards the Next Generation of Data Warehouse Personalization System A Survey and a Comparative Study
www.ijcsi.org 561 Towards the Next Generation of Data Warehouse Personalization System A Survey and a Comparative Study Saida Aissi 1, Mohamed Salah Gouider 2 Bestmod Laboratory, University of Tunis, High
When to consider OLAP?
When to consider OLAP? Author: Prakash Kewalramani Organization: Evaltech, Inc. Evaltech Research Group, Data Warehousing Practice. Date: 03/10/08 Email: erg@evaltech.com Abstract: Do you need an OLAP
ETL evolution from data sources to data warehouse using mediator data storage
ETL evolution from data sources to data warehouse using mediator data storage Alexander Dolnik (alexander.dolnik@gmail.com) Saint-Petersburg State University Abstract. The problem of evolution in the ETL
Slowly Changing Dimensions Specification a Relational Algebra Approach Vasco Santos 1 and Orlando Belo 2 1
Slowly Changing Dimensions Specification a Relational Algebra Approach Vasco Santos 1 and Orlando Belo 2 1 CIICESI, School of Management and Technology, Porto Polytechnic, Felgueiras, Portugal Email: vsantos@estgf.ipp.pt
www.ijreat.org Published by: PIONEER RESEARCH & DEVELOPMENT GROUP (www.prdg.org) 28
Data Warehousing - Essential Element To Support Decision- Making Process In Industries Ashima Bhasin 1, Mr Manoj Kumar 2 1 Computer Science Engineering Department, 2 Associate Professor, CSE Abstract SGT
A Brief Tutorial on Database Queries, Data Mining, and OLAP
A Brief Tutorial on Database Queries, Data Mining, and OLAP Lutz Hamel Department of Computer Science and Statistics University of Rhode Island Tyler Hall Kingston, RI 02881 Tel: (401) 480-9499 Fax: (401)
Part 22. Data Warehousing
Part 22 Data Warehousing The Decision Support System (DSS) Tools to assist decision-making Used at all levels in the organization Sometimes focused on a single area Sometimes focused on a single problem
Determining Preferences from Semantic Metadata in OLAP Reporting Tool
Determining Preferences from Semantic Metadata in OLAP Reporting Tool Darja Solodovnikova, Natalija Kozmina Faculty of Computing, University of Latvia, Riga LV-586, Latvia {darja.solodovnikova, natalija.kozmina}@lu.lv
Fuzzy Spatial Data Warehouse: A Multidimensional Model
4 Fuzzy Spatial Data Warehouse: A Multidimensional Model Pérez David, Somodevilla María J. and Pineda Ivo H. Facultad de Ciencias de la Computación, BUAP, Mexico 1. Introduction A data warehouse is defined
THE QUALITY OF DATA AND METADATA IN A DATAWAREHOUSE
THE QUALITY OF DATA AND METADATA IN A DATAWAREHOUSE Carmen Răduţ 1 Summary: Data quality is an important concept for the economic applications used in the process of analysis. Databases were revolutionized
Data warehouse Architectures and processes
Database and data mining group, Data warehouse Architectures and processes DATA WAREHOUSE: ARCHITECTURES AND PROCESSES - 1 Database and data mining group, Data warehouse architectures Separation between
Data Warehouse Architecture Overview
Data Warehousing 01 Data Warehouse Architecture Overview DW 2014/2015 Notice! Author " João Moura Pires (jmp@di.fct.unl.pt)! This material can be freely used for personal or academic purposes without any
A Survey on Data Warehouse Architecture
A Survey on Data Warehouse Architecture Rajiv Senapati 1, D.Anil Kumar 2 1 Assistant Professor, Department of IT, G.I.E.T, Gunupur, India 2 Associate Professor, Department of CSE, G.I.E.T, Gunupur, India
BUSINESS INTELLIGENCE AS SUPPORT TO KNOWLEDGE MANAGEMENT
ISSN 1804-0519 (Print), ISSN 1804-0527 (Online) www.academicpublishingplatforms.com BUSINESS INTELLIGENCE AS SUPPORT TO KNOWLEDGE MANAGEMENT JELICA TRNINIĆ, JOVICA ĐURKOVIĆ, LAZAR RAKOVIĆ Faculty of Economics
Data Warehousing and OLAP Technology for Knowledge Discovery
542 Data Warehousing and OLAP Technology for Knowledge Discovery Aparajita Suman Abstract Since time immemorial, libraries have been generating services using the knowledge stored in various repositories
University of Gaziantep, Department of Business Administration
University of Gaziantep, Department of Business Administration The extensive use of information technology enables organizations to collect huge amounts of data about almost every aspect of their businesses.
Basics of Dimensional Modeling
Basics of Dimensional Modeling Data warehouse and OLAP tools are based on a dimensional data model. A dimensional model is based on dimensions, facts, cubes, and schemas such as star and snowflake. Dimensional
1. OLAP is an acronym for a. Online Analytical Processing b. Online Analysis Process c. Online Arithmetic Processing d. Object Linking and Processing
1. OLAP is an acronym for a. Online Analytical Processing b. Online Analysis Process c. Online Arithmetic Processing d. Object Linking and Processing 2. What is a Data warehouse a. A database application
SDWM: An Enhanced Spatial Data Warehouse Metamodel
SDWM: An Enhanced Spatial Data Warehouse Metamodel Alfredo Cuzzocrea 1, Robson do Nascimento Fidalgo 2 1 ICAR-CNR & University of Calabria, 87036 Rende (CS), ITALY cuzzocrea@si.deis.unical.it. 2. CIN,
Data Warehouse Snowflake Design and Performance Considerations in Business Analytics
Journal of Advances in Information Technology Vol. 6, No. 4, November 2015 Data Warehouse Snowflake Design and Performance Considerations in Business Analytics Jiangping Wang and Janet L. Kourik Walker
CONTINUOUS DATA WAREHOUSE: CONCEPTS, CHALLENGES AND POTENTIALS
Geoinformatics 2004 Proc. 12th Int. Conf. on Geoinformatics Geospatial Information Research: Bridging the Pacific and Atlantic University of Gävle, Sweden, 7-9 June 2004 CONTINUOUS DATA WAREHOUSE: CONCEPTS,
SALES BASED DATA EXTRACTION FOR BUSINESS INTELLIGENCE
SALES BASED DATA EXTRACTION FOR BUSINESS INTELLIGENCE Sukanta Singh Department of Computer Science & Engineering, Global Institute of Management & Technology, Krishnagar, Nadia, West Bengal sukantasingh2008@gmail.com
RESEARCH ON THE FRAMEWORK OF SPATIO-TEMPORAL DATA WAREHOUSE
RESEARCH ON THE FRAMEWORK OF SPATIO-TEMPORAL DATA WAREHOUSE WANG Jizhou, LI Chengming Institute of GIS, Chinese Academy of Surveying and Mapping No.16, Road Beitaiping, District Haidian, Beijing, P.R.China,
Social Network Engineering for Secure Web Data and Services
Social Network Engineering for Secure Web Data and Services Luca Caviglione National Research Council of Italy, Italy Mauro Coccoli University of Genoa, Italy Alessio Merlo University of Genoa, Italy &
Dimensional Modeling
Dimensional Modeling Krzysztof Dembczyński Intelligent Decision Support Systems Laboratory (IDSS) Poznań University of Technology, Poland Software Development Technologies Master studies, first semester
Trivadis White Paper. Comparison of Data Modeling Methods for a Core Data Warehouse. Dani Schnider Adriano Martino Maren Eschermann
Trivadis White Paper Comparison of Data Modeling Methods for a Core Data Warehouse Dani Schnider Adriano Martino Maren Eschermann June 2014 Table of Contents 1. Introduction... 3 2. Aspects of Data Warehouse
DATA WAREHOUSING AND OLAP TECHNOLOGY
DATA WAREHOUSING AND OLAP TECHNOLOGY Manya Sethi MCA Final Year Amity University, Uttar Pradesh Under Guidance of Ms. Shruti Nagpal Abstract DATA WAREHOUSING and Online Analytical Processing (OLAP) are
Encyclopedia of Database Technologies and Applications. Data Warehousing: Multi-dimensional Data Models and OLAP. Jose Hernandez-Orallo
Encyclopedia of Database Technologies and Applications Data Warehousing: Multi-dimensional Data Models and OLAP Jose Hernandez-Orallo Dep. of Information Systems and Computation Technical University of
Index Selection Techniques in Data Warehouse Systems
Index Selection Techniques in Data Warehouse Systems Aliaksei Holubeu as a part of a Seminar Databases and Data Warehouses. Implementation and usage. Konstanz, June 3, 2005 2 Contents 1 DATA WAREHOUSES
Requirements are elicited from users and represented either informally by means of proper glossaries or formally (e.g., by means of goal-oriented
A Comphrehensive Approach to Data Warehouse Testing Matteo Golfarelli & Stefano Rizzi DEIS University of Bologna Agenda: 1. DW testing specificities 2. The methodological framework 3. What & How should
Data Model ing Essentials
Data Model ing Essentials Third Edition Graeme C. Simsion and Graham C. Witt MORGAN KAUFMANN PUBLISHERS AN IMPRINT OF ELSEVIER AMSTERDAM BOSTON LONDON NEW YORK OXFORD PARIS SAN DIEGO SAN FRANCISCO SINGAPORE
The Benefits of Data Modeling in Business Intelligence. www.erwin.com
The Benefits of Data Modeling in Business Intelligence Table of Contents Executive Summary...... 3 Introduction.... 3 Why Data Modeling for BI Is Unique...... 4 Understanding the Meaning of Information.....
Terminology and Definitions. Data Warehousing and OLAP. Data Warehouse characteristics. Data Warehouse Types. Typical DW Implementation
Data Warehousing and OLAP Topics Introduction Data modelling in data warehouses Building data warehouses View Maintenance OLAP and data mining Reading Lecture Notes Elmasriand Navathe, Chapter 26 Ozsu
DEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES
DEVELOPING REQUIREMENTS FOR DATA WAREHOUSE SYSTEMS WITH USE CASES Robert M. Bruckner Vienna University of Technology bruckner@ifs.tuwien.ac.at Beate List Vienna University of Technology list@ifs.tuwien.ac.at
Sales and Operations Planning in Company Supply Chain Based on Heuristics and Data Warehousing Technology
Sales and Operations Planning in Company Supply Chain Based on Heuristics and Data Warehousing Technology Jun-Zhong Wang 1 and Ping-Yu Hsu 2 1 Department of Business Administration, National Central University,
Essbase Integration Services Release 7.1 New Features
New Features Essbase Integration Services Release 7.1 New Features Congratulations on receiving Essbase Integration Services Release 7.1. Essbase Integration Services enables you to transfer the relevant
Database Design Overview. Conceptual Design ER Model. Entities and Entity Sets. Entity Set Representation. Keys
Database Design Overview Conceptual Design. The Entity-Relationship (ER) Model CS430/630 Lecture 12 Conceptual design The Entity-Relationship (ER) Model, UML High-level, close to human thinking Semantic
THE INTELLIGENT BUSINESS INTELLIGENCE SOLUTIONS
THE INTELLIGENT BUSINESS INTELLIGENCE SOLUTIONS ADRIAN COJOCARIU, CRISTINA OFELIA STANCIU TIBISCUS UNIVERSITY OF TIMIŞOARA, FACULTY OF ECONOMIC SCIENCE, DALIEI STR, 1/A, TIMIŞOARA, 300558, ROMANIA ofelia.stanciu@gmail.com,
TIM 50 - Business Information Systems
TIM 50 - Business Information Systems Lecture 15 UC Santa Cruz March 1, 2015 The Database Approach to Data Management Database: Collection of related files containing records on people, places, or things.
14. Data Warehousing & Data Mining
14. Data Warehousing & Data Mining Data Warehousing Concepts Decision support is key for companies wanting to turn their organizational data into an information asset Data Warehouse "A subject-oriented,
Continuous Spatial Data Warehousing
Continuous Spatial Data Warehousing Taher Omran Ahmed Faculty of Science Aljabal Algharby University Azzentan - Libya Taher.ahmed@insa-lyon.fr Abstract Decision support systems are usually based on multidimensional
Upon successful completion of this course, a student will meet the following outcomes:
College of San Mateo Official Course Outline 1. COURSE ID: CIS 364 TITLE: Enterprise Data Warehousing Semester Units/Hours: 4.0 units; a minimum of 48.0 lecture hours/semester; a minimum of 48.0 lab hours/semester
Subject Description Form
Subject Description Form Subject Code Subject Title COMP417 Data Warehousing and Data Mining Techniques in Business and Commerce Credit Value 3 Level 4 Pre-requisite / Co-requisite/ Exclusion Objectives
Foundations of Business Intelligence: Databases and Information Management
Chapter 5 Foundations of Business Intelligence: Databases and Information Management 5.1 Copyright 2011 Pearson Education, Inc. Student Learning Objectives How does a relational database organize data,
META DATA QUALITY CONTROL ARCHITECTURE IN DATA WAREHOUSING
META DATA QUALITY CONTROL ARCHITECTURE IN DATA WAREHOUSING Ramesh Babu Palepu 1, Dr K V Sambasiva Rao 2 Dept of IT, Amrita Sai Institute of Science & Technology 1 MVR College of Engineering 2 asistithod@gmail.com
SENG 520, Experience with a high-level programming language. (304) 579-7726, Jeff.Edgell@comcast.net
Course : Semester : Course Format And Credit hours : Prerequisites : Data Warehousing and Business Intelligence Summer (Odd Years) online 3 hr Credit SENG 520, Experience with a high-level programming
Encyclopedia of Distance Learning Second Edition
Encyclopedia of Distance Learning Second Edition Patricia Rogers Bemidji State, USA Gary Berg Chapman University, USA Judith Boettcher Designing for Learning, USA Carole Howard Touro University International,
Understanding Data and Information Systems for Recordkeeping. by Philip C. Bantin
Contents i Understanding Data and Information Systems for Recordkeeping by Philip C. Bantin The Archives & Record Manager s Bookshelf 2 Neal-Schuman Publishers, Inc. New York London Published by Neal-Schuman
The Data Warehouse ETL Toolkit
2008 AGI-Information Management Consultants May be used for personal purporses only or by libraries associated to dandelon.com network. The Data Warehouse ETL Toolkit Practical Techniques for Extracting,
Alexander Nikov. 5. Database Systems and Managing Data Resources. Learning Objectives. RR Donnelley Tries to Master Its Data
INFO 1500 Introduction to IT Fundamentals 5. Database Systems and Managing Data Resources Learning Objectives 1. Describe how the problems of managing data resources in a traditional file environment are
Balancing of Business Data Model and Transactional Data Model
Balancing of Business Data Model and ransactional Data Model Y. Sri Veni, Y. Pratap Abstract he business information oriented system and enterprise data both are equally essential and important for an
Conceptual Multidimensional Models
Conceptual Multidimensional Models Chapter in the Book: Multidimensional Databases Maurizio Rafanelli Ed. RICCARDO TORLONE Dip. di Informatica e Automazione Università Roma Tre Via della Vasca Navale,