DOCSLIB.ORG

Data Vault Modeling & Methodology

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Data Vault Modeling & Methodology Data Vault Modeling & Methodology Technical Side and Introduction © Dan Linstedt, 2010, http://DanLinstedt.com Technical Definition The Data Vault is a detail oriented, historical tracking and uniquely linked set of normalized tables that support one or more functional areas of business. It is a hybrid approach encompassing the best of breed between 3rd normal form (3NF) and star schema. The design is flexible, scalable, consistent and adaptable to the needs of the enterprise. Architected specifically to meet the needs of today’s enterprise data warehouses 5/28/2010 http://empoweredHoldings.com 2 What Does One Look Like? Records a history Customer of the interaction Product Sat Sat Elements: Sat •Hub •Link Sat Customer Link Product Sat •Satellite F(x) Sat F(x) F(x) Sat Sat Hub = List of Unique Business Keys Order Sat Link = List of Relationships, Associations Satellites = Descriptive Data F(x) Sat Order 5/28/2010 http://empoweredHoldings.com 3 Excel As A Source… HierarchicalHierarchical Level A LinkLink ofof GroupsGroups Level B Level C HubHub GroupingGrouping Item SatSat GroupGroup TypeType Item Item Staging Table LinkLink AcctAcct ToTo GroupGroup User Grouping Structures Flattened Structure Raw Source HubHub AccountAccount Data in DV Do you have a power executive who is technically inclined, who runs the business off a rogue spreadsheet? 5/28/2010 http://empoweredHoldings.com 4 Data Vault Basic Elements CORE ARCHITECTURE 5/28/2010 http://empoweredHoldings.com 5 Data Vault Core Architecture • Hubs, Links, Satellites • Hubs = Unique List of Business Keys • Links = Unique List of Relationships across keys • Satellites = Descriptive Data • Satellites have 1 and only one parent table • Satellites cannot be “Parents” to other tables • Hubs cannot be child tables • Last Seen Dates, Load Dates, Record Sources, and Surrogate keys are not part of the core architecture. They exists to help models and key migration. 5/28/2010 http://empoweredHoldings.com 6 Hub Entity A Hub is a list of unique business keys Hub Structure Hub Product Primary Key Product Sequence ID Unique Index <Business Key> (Primary Index) Product Number Load DTS Product Load DTS Last Seen DTS Product Last Seen DTS Record Source Prod Record Source • A Hub’s business key is a unique index • A Hub’s load date represents the FIRST TIME the EDW saw the data • A Hub’s record source represents: First – the “Master” data source (on collisions), if not available it holds the origination source of the actual key 5/28/2010 http://empoweredHoldings.com 7 Link Entity A Link is an intersection of two or more business keys It can contain Hub keys and other Link keys Link Structure Link Line-Item Primary Key Link Line Item Sequence ID {Hub/Lnk Surrogate Keys 2..N} Unique Index Hub Product Sequence ID Load DTS (Primary Index) Hub Order Sequence ID Last Seen DTS **Line Item Number Record Source Load DTS Last Seen DTS Record Source A Link’s business key is a composite unique index • A Link may or may not have a “**Item Numbering” attribute • A Link’s load date represents the FIRST TIME the EDW saw the data • A Link’s record source represents: first – the “Master” data source (on collisions), if not available, it holds the origination source of the actual key 5/28/2010 http://empoweredHoldings.com 8 Satellite Entity A Satellite is a time-dimensional table housing detailed information about the Hub’s or Link’s business keys Primary Key Unique Index Customer # Load DTS (Primary Index) Load DTS Extract DTS Extract DTS **Load End Date **Load End Date Detail Customer Name Business Data Customer Addr1 Customer Addr2 {Update User} {Update User} {Update DTS} {Update DTS} Record Source Record Source • Satellites are defined by TYPE of data and RATE OF CHANGE • Mathematically – this reduces redundancy and decreases storage requirements over time (compared to a star schema) 5/28/2010 http://empoweredHoldings.com 9 Rules and Standards GOVERN your deployment… THINKING OF BREAKING RULES… 5/28/2010 http://empoweredHoldings.com 10 Some Rules For You • NO Foreign Keys in the Satellites! • NO Hub to Hub (Parent Child relationships) • NO Enforcement of relationships in the data model… • NO Date Time attributes in HUB or LINK Primary Keys… •Why?? – It breaks flexibility – It breaks auditability / accountability – It breaks Scalability – It breaks Performance – It introduces “Decisions” in the architecture, which breaks Patterns! Up Next Æ Links and the Unit Of Work… 5/28/2010 http://empoweredHoldings.com 11 Business Key Definitions… • “The contracts system is responsible for creating customer account numbers. The EDW will never see other systems creating customer account numbers.” (Requirement #101) Sales is clearly creating customer numbers, how do we detect the issue and alert the business? Point: Not all business keys are created EQUAL! 5/28/2010 http://empoweredHoldings.com 12 Link: Unit of Work Hub Category Link Sat Effectivity Prod-Cat Unit Of Work Link Hub Product Link: Product by Line Item Supplier by Category Link Sat Effectivity Prod-Supp Hub Supplier Link Product by Category These links are Optional, used Link Product by Supplier For exploration only 5/28/2010 http://empoweredHoldings.com 13 What Happens When: We Break the Unit of Work Link Product by Supplier Source System UOW Product_ID Supplier_ID Product_ID Category_ID Supplier_ID 222 96 222 12 96 222 93 222 12 93 729 87 729 15 87 Link Product by Category 222 17 93 Product_ID Category_ID Model Normalization 222 12 222 17 729 15 Question: After normalizing, how can you reconstruct the source image EXACLTY as it stands? 5/28/2010 http://empoweredHoldings.com 14 What Happens When: Trying to Rebuild from Two Links Link Product by Supplier Source System UOW Product_ID Supplier_ID Product_ID Category_ID Supplier_ID 222 96 222 12 96 222 93 222 12 93 729 87 222 17 96 Link Product by Category 222 17 93 Product_ID Category_ID Model 729 15 87 Normalization 222 12 222 17 729 15 Re-joining the data, creates a record that does not exist in the original source system, this is the same problem that BI engines will have when putting together Data Mart results. 5/28/2010 http://empoweredHoldings.com 15 Link: Unit of Work Kept Together Source System Data Vault Source Table UOW Link: Product by Category by Supplier Product_ID Category_ID Supplier_ID Product_ID Category_ID Supplier_ID 222 12 96 222 12 96 222 12 93 222 12 93 729 15 87 729 15 87 222 17 93 222 17 93 Commutative Property: Enable reproduction of the source exactly as it stands UOW is properly represented by a single Link in the Data Vault 5/28/2010 http://empoweredHoldings.com 16 What keeps you up at night? CURRENT LOADING PAIN 5/28/2010 http://empoweredHoldings.com 17 Problems with EDW Loads Today Technical Issues: • 2am Wakeup Calls – because “data” won’t fit the business rules • “Emergency Fixes” to Production • Speed, Speed, Speed (shrinking load window + more data) • Can’t load real-time data (business rules in the way!!) • Business won’t buy better, faster, hardware! Business Issues: • Maintenance cycles take too long • Maintenance costs continue to increase • Fixes to “existing mappings” break working logic • Complexity of existing systems become unsustainable to business • IT isn’t using 80%+ of the hardware resources given to them (their jobs are running at 40% utilization when they are “full-bore”) 5/28/2010 http://empoweredHoldings.com 18 Solutions! Technical Solutions • All Parallel Job Streams As much as possible • 1 Target Per Map, Per Action Æ reduces complexity • Generate Data Flows based on patterns (then focus on the real work) • Get some SLEEP at night!! (no more production modifications) Business Solutions • Decrease turn-around time • Increase Performance • Handle Real-Time Data!! • Reduce Complexity = Reduce Costs, Reduce Time to Implement • Get the power back for decision making, discovering and building your own marts 5/28/2010 http://empoweredHoldings.com 19 How? 5/28/2010 http://empoweredHoldings.com 20 Some standards to follow… BASIC LOADING CONCEPTS 5/28/2010 http://empoweredHoldings.com 21 Loading: A Golden Rule 100% of the Data Loaded to the EDW 100% of the time! It’s all about Auditability… 5/28/2010 http://empoweredHoldings.com 22 Load Date / End Date Geology Batch Load Real-Time Loading 5/28/2010 http://empoweredHoldings.com 23 Real Time Loading - DV Acct Hub Stock Trade 123443576 ACCOUNT=123443576 1 TRADE="Buy" STOCK=“DAN" TRADE="Buy" SHARES=100.0 SHARES=100.0 CURRENCY="USD" Trade Link CURRENCY="USD" 3 PRICE=115.52 PRICE=115.52 DATE="Feb 20, 2002“ DATE="Feb 20, 2002“ Comment="Buy Order to Execute" Comment="Buy Order to Execute" 2 “DAN” Transactional Link = Inserts Only, no Updates Stock Hub • As critical mass of current business 75M First Data Set Loaded keys is reached, the insert rates # of 50M decrease rapidly. Inserts 25M New Systems Data Added 10M • New systems add new keys, quickly and efficiently to an existing Hub. 1 2 345678 Months in Production 5/28/2010 http://empoweredHoldings.com 24 Batch Load Date Time Stamp Staging Area EDW – Data Vault CNTRL_DTE LOAD_DTS Load Date Is exactly the same STAGING TABLE For All rows Sequence_ID Stage Load …. Load_DTS Record_Source Stage Load STAGING TABLE Sequence_ID …. Load_DTS Record_Source 5/28/2010 http://empoweredHoldings.com 25 Parallel Load Architecture - Batch Staging Loads Data Vault Loads Data Mart Loads Hub Link Sources Stage Hubs Satellites Satellites Dimensions Facts Links Major Synchronization Points Processing: • All loads are done in parallel • Sets of processes “wait” for the previous set to complete
Load more

Recommended publications
  • Star Schema Modeling with Pentaho Data Integration
    Star Schema Modeling With Pentaho Data Integration Saurischian and erratic Salomo underworked her accomplishment deplumes while Phil roping some diamonds believingly. Torrence elasticize his umbrageousness parsed anachronously or cheaply after Rand pensions and darn postally, canalicular and papillate. Tymon trodden shrinkingly as electropositive Horatius cumulates her salpingectomies moat anaerobiotically. The email providers have a look at pentaho user console files from a collection, an individual industries such processes within an embedded saiku report manager. The database connections in data modeling with schema. Entity Relationship Diagram ERD star schema Data original database creation. For more details, the proposed DW system ran on a Windowsbased server; therefore, it responds very slowly to new analytical requirements. In this section we'll introduce modeling via cubes and children at place these models are derived. The data presentation level is the interface between the system and the end user. Star Schema Modeling with Pentaho Data Integration Tutorial Details In order first write to XML file we pass be using the XML Output quality This is. The class must implement themondrian. Modeling approach using the dimension tables and fact tables 1 Introduction The use. Data Warehouse Dimensional Model Star Schema OLAP Cube 5. So that will not create a lot when it into. But it will create transformations on inventory transaction concepts, integrated into several study, you will likely send me? Thoughts on open Vault vs Star Schemas the bi backend. Table elements is data integration tool which are created all the design to the farm before with delivering aggregated data quality and data is preventing you.
    [Show full text]
  • Data Vault and 'The Truth' About the Enterprise Data Warehouse
    Data Vault and ‘The Truth’ about the Enterprise Data Warehouse Roelant Vos – 04-05-2012 Brisbane, Australia Introduction More often than not, when discussion about data modeling and information architecture move towards the Enterprise Data Warehouse (EDW) heated discussions occur and (alternative) solutions are proposed supported by claims that these alternatives are quicker and easier to develop than the cumbersome EDW while also delivering value to the business in a more direct way. Apparently, the EDW has a bad image. An image that seems to be associated with long development times, high complexity, difficulties in maintenance and a falling short on promises in general. It is true that in the past many EDW projects have suffered from stagnation during the data integration (development) phase. These projects have stalled in a cycle of changes in ETL and data model design and the subsequent unit and acceptance testing. No usable information is presented to the business users while being stuck in this vicious cycle and as a result an image of inability is painted by the Data Warehouse team (and often at high costs). Why are things this way? One of the main reasons is that the Data Warehouse / Business Intelligence industry defines and works with The Enterprise Data architectures that do not (can not) live up to their promises. To date Warehouse has a bad there are (still) many Data Warehouse specialists who argue that an image while in reality it is EDW is always expensive, complex and monolithic whereas the real driven by business cases, message should be that an EDW is in fact driven by business cases, adaptive and quick to adaptive and quick to deliver.
    [Show full text]
  • QUIPU 1.1 Whitepaper Final
    WHITEPAPER QUIPU version 1.1 OPEN SOURCE DATAWAREHOUSING QUIPU 1.1 Whitepaper Contents Introduction .................................................................................................................................................................................................................. 4 QUIPU ................................................................................................................................................................................................................ 4 History ................................................................................................................................................................................................................. 4 Data warehouse architecture ................................................................................................................................................................................. 6 Starting points .................................................................................................................................................................................................. 6 Modeling ............................................................................................................................................................................................................ 7 Core components of QUIPU .................................................................................................................................................................
    [Show full text]
  • Integration of Heterogeneous Data in the Data Vault Model
    Institute for Parallel and Distributed Systems Universität Stuttgart Universitätsstraße 38 70569 Stuttgart Germany Master Thesis Integration of Heterogeneous Data in the Data Vault Model Geethanjali Nataraj Study Program: Computer Science Examiner: Dr. Holger Schwarz Advisor: Corinna Giebler, M.Sc. Informatik Start Date: 17. July 2018 End Date: 17. January 2019 Abstract Data increases tremendously with respect to volume, velocity, and variety. Nowadays, most of these data are unstructured like text documents, images, videos, Internet of Things (IoT) data, etc. Especially in enterprises, the analysis of semi-structured and unstructured data together with traditional structured data can add value. For example, semi-structured email data can be combined with structured customer data to keep a complete record of all customer information. Likewise, unstructured IoT data can be combined with structured machine data to enable predictive maintenance. Thereby, heterogeneous data need to be efficiently stored, integrated, and analyzed to derive useful business insights. The traditional modeling techniques like Kimball’s approach and Inmon’s approach are primarily focused on modeling structured data. Due to vast amounts of data being collected and agile project execution, scalability and flexibility become more essential characteristics in data modeling. However, especially regarding flexibility, the traditional data modeling approaches used in data warehousing face some limitations. Therefore, Data Vault modeling was developed to overcome these limitations. However, the Data Vault model was designed for structured data. To combine these structured data with semi-structured and unstructured data, the Data Vault model therefore needs to be adapted. However, there exists no comprehensive approach to do so for both semi-structured and unstructured data.
    [Show full text]
  • Data Vault Modelling
    Awel Eshetu Fentaw Data Vault Modelling An Introductory Guide Helsinki Metropolia University of Applied Sciences Bachelor of Engineering Information Technology Thesis 31 March 2014 Abstract Author(s) Awel Eshetu Fentaw Title Data Vault Modelling: An Introductory Guide Degree Bachelor of Engineering Degree Programme Information Technology Specialisation option Software Engineering Instructor(s) Olli Hämäläinen, Senior Lecturer The theme of this thesis is to prepare an introductory guide to Data Vault Modelling. The Data Vault is a relatively new method of modelling enterprise data warehouses. The Data Vault uses three core components to model an entire data warehouse. Thus it provides an easy alternate solution for data warehousing. The thesis project was conducted by researching books, scientific journal articles, profes- sional blog posts and professional community discussions. By doing so scattered infor- mation about Data Vault Modelling was gathered and analysed and compiled in to a guidebook. This paper could be used as a quick guidebook for those interested in finding information about Data Vault Modelling. Data Vault is a relatively new solution to enterprise data warehousing. Although it intro- duces a better way of modelling enterprise data warehouses, it still has limitations when it comes to providing strict guidelines and handling unstructured text, semi-structured Doc Style data, XML and other data types which are broadly known as Big Data. These data types cannot be handled using the current approaches, tools and techniques; however there is an ongoing research to make the Data Vault Model be able to handle such Big Data. Thus this thesis includes only officially published articles about Data Vault.
    [Show full text]
  • Data Vault Modeling the Next Generation DW Approach
    Data Vault Modeling The Next Generation DW Approach Presented by: Siva Govindarajan http://www.globytes.com [email protected] 1 Data Vault Modeling Agenda Introduction Data Vault Place in Evolution Data Warehousing Architecture Data Vault Components Case Study Typical 3NF / Star Schema Data Vault Approach Temporal Data + Auditability Implementation of Data Vault Conclusion 2 Introduction Data Vault concept originally conceived by Dan Linstedt Enterprise Data Warehouse Modeling approach. Hybrid approach - 3NF & Star Schema Adaptable to changes Auditable Timed right with Technology 3 Data Vault Place in Evolution 1960s - Codd, Date et. al Normal Forms 1980s - Normal Forms adapted to DWs 1985+ - Star Schema for OLAP 1990s - Data Vault concept developed Dan Linstedt 2000+ - Data Vault concept published by Dan Linstedt 4 Data Warehousing Architecture Bill Inmon’s Data Warehouse Architecture Data Mart OLTP Enterprise Staging Data Mart Staging Data Marts (optional) Data Marts Systems & ODS DW e tiv s p rt da a A M Kimball’s Data Warehouse Bus Architecture Data Mart Data Mart OLTP Systems Staging Data Mart Data Mart 5 Data Vault Components Hub Entities Candidate Keys + Load Time + Source Link Entities FKs from Hub + Load Time + Source Satellite Entities Descriptive Data + Load Time + Source + End Time Dimension = Hub+ Satellite Fact = Satellite + Link [+ Hub ] 6 Case Study Modeling Approaches Typical 3NF / Star Schema Data Vault approach Scenario Typical Fact and Dimension New Dimension data Reference Data change - 1:M to M:M Additional attributes to Dimension 7 Typical 3F / Star Schema 1. Typical Fact and Dimension TR ORDER DIM PRODUCT tr_order_id dim_product_id dim_product_id product_id system order id product_code system root order id product desc global root order id product_name order quantity le ngth total executed qty event timestamp 8 Typical 3F / Star Schema 2.
    [Show full text]
  • Data Warehouse and Master Data Management Evolution – a Meta-Data-Vault Approach
    https://doi.org/10.48009/2_iis_2014_14-23 Issues in Information Systems Volume 15, Issue II, pp. 14-23, 2014 DATA WAREHOUSE AND MASTER DATA MANAGEMENT EVOLUTION – A META-DATA-VAULT APPROACH Danijela Subotic, Department of Informatics/University of Rijeka, [email protected] Vladan Jovanovic, Georgia Southern University, [email protected] Patrizia Poscic, Department of Informatics/University of Rijeka, [email protected] ABSTRACT The paper presents a: a) brief overview and analysis of existing approaches to the data warehouse (DW) evolution problem, and b) detailed description of the research idea for the DW evolution problem (primarily intended for structured data sources and realizations with relational database engines). We observe the DW evolution problem as a double issue - from the DW perspective, and from the master data management (MDM) perspective. The proposed general solution will include a Data Vault (DV) model based metadata repository that will integrate the DW data and metadata with the MDM data and metadata. This historicized metadata repository will manage schema versions and support schema changes. We believe this integration will: a) increase the quality of data in the Enterprise Data Warehouse (EDW), b) increase the quality of the metadata in the EDW, and c) increase the simplicity and efficiency of the DW and the MDM schema evolution. Keywords: data warehouse evolution, master data management, data vault, metadata repository, schema evolution, schema versioning, view maintenance INTRODUCTION A data warehouse (DW) integrates current and historical data from a number of heterogeneous data sources into a central repository of data which is then used for business reporting, trend projections and quick data analysis.
    [Show full text]
  • Building Open Source ETL Solutions with Pentaho Data Integration
    Pentaho® Kettle Solutions Pentaho® Kettle Solutions Building Open Source ETL Solutions with Pentaho Data Integration Matt Casters Roland Bouman Jos van Dongen Pentaho® Kettle Solutions: Building Open Source ETL Solutions with Pentaho Data Integration Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 lll#l^aZn#Xdb Copyright © 2010 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-0-470-63517-9 ISBN: 9780470942420 (ebk) ISBN: 9780470947524 (ebk) ISBN: 9780470947531 (ebk) Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appro- priate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at ]iie/$$lll#l^aZn#Xdb$\d$eZgb^hh^dch. Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representa- tions or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose.
    [Show full text]
  • Testing Data Vault-Based Data Warehouse
    Georgia Southern University Digital Commons@Georgia Southern Electronic Theses and Dissertations Graduate Studies, Jack N. Averitt College of Fall 2015 Testing Data Vault-Based Data Warehouse Connard N. Williams Follow this and additional works at: https://digitalcommons.georgiasouthern.edu/etd Part of the Computer and Systems Architecture Commons, Databases and Information Systems Commons, Data Storage Systems Commons, and the Software Engineering Commons Recommended Citation Williams, Connard N., "Testing Data Vault-Based Data Warehouse" (2015). Electronic Theses and Dissertations. 1340. https://digitalcommons.georgiasouthern.edu/etd/1340 This thesis (open access) is brought to you for free and open access by the Graduate Studies, Jack N. Averitt College of at Digital Commons@Georgia Southern. It has been accepted for inclusion in Electronic Theses and Dissertations by an authorized administrator of Digital Commons@Georgia Southern. For more information, please contact [email protected]. 1 TESTING DATA VAULT-BASED DATA WAREHOUSE by CONNARD N. WILLIAMS (Under the Direction of Vladan Jovanovic) ABSTRACT Data warehouse (DW) projects are undertakings that require integration of disparate sources of data, a well-defined mapping of the source data to the reconciled data, and effective Extract, Transform, and Load (ETL) processes. Owing to the complexity of data warehouse projects, great emphasis must be placed on an agile-based approach with properly developed and executed test plans throughout the various stages of designing, developing, and implementing the data warehouse to mitigate against budget overruns, missed deadlines, low customer satisfaction, and outright project failures. Yet, there are often attempts to test the data warehouse exactly like traditional back-end databases and legacy applications, or to downplay the role of quality assurance (QA) and testing, which only serve to fuel the frustration and mistrust of data warehouse and business intelligence (BI) systems.
    [Show full text]
  • Raman & Cata Data Vault Modeling and Its Evolution
    Raman & Cata Data Vault Modeling and its Evolution _____________________________________________________________________________________ DECISION SCIENCES INSTITUTE Conceptual Data Vault Modeling and its Opportunities for the Future Aarthi Raman, Active Network, Dallas, TX, 75201 [email protected] Teuta Cata, Northern Kentucky University, Highland Heights, KY, 41099 [email protected] ABSTRACT This paper presents conceptual view of Data Vault Modeling (DVM), its architecture and future opportunities. It also covers concepts and definitions of data warehousing, data model by Kimball and Inmon and its evolution towards DVM. This approach is illustrated using a realistic example of the Library Management System. KEYWORDS: Conceptual Data Vault, Master Data Management, Extraction Transformation Loading INTRODUCTION This paper explains the scope, introduces basic terminologies, explains the requirements for designing a Data Vault (DV) type data warehouse, and explains its association. The design of DV is based on Enterprise Data Warehouse (EDW)/ Data Mart (DM). A Data Warehouse is defined as: “a subject oriented, non-volatile, integrated, time variant collection of data in support management’s decisions” by Inmon (1992). A data warehouse can also be used to support the everlasting system of records and compliance and improved data governance (Jarke M, Lenzerini M, Vassiliou Y, Vassiliadis P, 2003). Data Marts are smaller Data Warehouses that constitute only a subset of the Enterprise Data Warehouse. An important feature of Data Marts is they provide a platform for Online Analytical Processing Analysis (OLAP) (Ćamilović D., Bečejski-Vujaklija D., Gospić N, 2009). Therefore, OLAP is a natural extension of a data warehouse (Krneta D., Radosav D., Radulovic B, 2008). Data Marts are a part of data storage, which contains summarized data.
    [Show full text]
  • Building a Scalable Data Warehouse with Data Vault 2.0
    Building a Scalable Data Warehouse with Data Vault 2.0 Daniel Linstedt Michael Olschimke • • AMSTERDAM • BOSTON HEIDELBERG LONDON • • NEWYORK • OXFORD PARIS SAN DIEGO SAN FRANCISCO • SINGAPORE • SYDNEY • TOKYO M< Morgan Kaufmann is an Imprint of Elsevier Contents Authors Biography xiii Foreword xv Preface xvii Acknowledgments xix CHAPTER 1 Introduction to Data Warehousing 1 1.1 History of Data Warehousing 2 1.1.1 Decision Support Systems 3 1.1.2 Data Warehouse Systems 4 1.2 The Enterprise Data Warehouse Environment 5 1.2.1 Access 5 1.2.2 Multiple Subject Areas 5 1.2.3 Single Version of Truth 5 1.2.4 Single Version of Facts 6 1.2.5 Mission Criticality 6 1.2.6 Scalability 6 1.2.7 Big Data 7 1.2.8 Performance Issues 7 1.2.9 Complexity 8 1.2.10 Auditing and Compliance 9 1.2.11 Costs 10 1.2.12 Other Business Requirements 11 1.3 Introduction to Data Vault 2.0 11 1.4 Data Warehouse Architecture 12 1.4.1 Typical Two-Layer Architecture 12 1.4.2 Typical Three-Layer Architecture 13 References 14 CHAPTER 2 Scalable Data Warehouse Architecture 17 2.1 Dimensions of Scalable Data Warehouse Architectures 17 2.1.1 Workload 18 2.1.2 Data Complexity 18 2.1.3 Analytical Complexity 19 2.1.4 Query Complexity 19 2.1.5 Availability 20 2.1.6 Security 20 Please refer the companion site for more details — http://booksite.elsevier.com/9780128025109 V vi Contents 2.2 Data Vault 2.0 Architecture 21 2.2.1 Business Rules Definition 22 2.2.2 Business Rules Application 23 2.2.3 Staging Area Layer 25 2.2.4 Data Warehouse Layer 26 2.2.5 Information Mart Layer 27 2.2.6 Metrics
    [Show full text]
  • Effectiveness of Data Vault Compared to Dimensional Data Marts on Overall Performance of a Data Warehouse System
    IJCSI International Journal of Computer Science Issues, Volume 13, Issue 4, July 2016 ISSN (Print): 1694-0814 | ISSN (Online): 1694-0784 www.IJCSI.org http://dx.doi.org/10.20943/01201604.1631 16 Effectiveness of Data Vault compared to Dimensional Data Marts on Overall Performance of a Data Warehouse System Zaineb Naamane1, Vladan Jovanovic2 1 Computer Science Department, Georgia Southern University Statesboro, 30458, USA 2 Computer Science Department, Georgia Southern University Statesboro, 30458, USA Abstract The purpose of this pilot study was to compare the The common assumption about DW is that once created it traditional Kimball’s approach (using star schemas remains static. This is incorrect because business needs Dimensional Model, directly from the data sources source) change and increase with time, and business processes are to define Data Marts vs. newest Linstedt’s approach (using subject to frequent change. As a consequence of this Data Vault 2.0 modeling of EDW with virtual/materialized change, a new type of information requirement that Data Marts as star schemas). The comparison is performed requires different data becomes necessary. These new experimentally using a specifically designed, realistic and requirements lead to changes in the DW schema and need broadly applicable case study. The study includes to be incorporated in the data warehouse system while implementing a Customer Experience Data Mart in the ensuring accurate insight of the business data. The data telecommunication domain extending the work done by the warehouse should be designed in a way that allows TM Forum’s standards/guidelines demonstrating a flexibility, evolution, and scalability. Moreover, as data feasibility of a complete implementation.
    [Show full text]