Towards Data Warehouse Quality Metrics

Total Page:16

File Type:pdf, Size:1020Kb

Towards Data Warehouse Quality Metrics Towards Data Warehouse Quality Metrics Coral Calero Mario Piattini ALARCOS Research Group ALARCOS Research Group University of Castilla-La Mancha (Spain) University of Castilla-La Mancha (Spain) Rda. Calatrava s/n 13071 Ciudad Real - Spain Rda. Calatrava s/n 13071 Ciudad Real - Spain [email protected] [email protected] Carolina Pascual Manuel A. Serrano ALARCOS Research Group ALARCOS Research Group University of Castilla-La Mancha (Spain) University of Castilla-La Mancha (Spain) Rda. Calatrava s/n 13071 Ciudad Real - Spain Rda. Calatrava s/n 13071 Ciudad Real - Spain [email protected] [email protected] process” [INM96]. Data warehouses have become the key trend in corporate computing in the last years, since they Abstract provide managers with the most accurate and relevant information to improve strategic decisions. Jarke et al. Organizations are adopting datawarehouses to [JAR00] forecast a 12 Millions American dollars for the manage information efficiently as “the” main data warehouse market. organizational asset. It is essential that we can Different life cycles and techniques have been assure the information quality of the data proposed for data warehouse development [HAM96] warehouse, as it became the main tool for [KEL97] [KIM98]. However the development of a data strategic decisions. Information quality depends warehouse is a difficult and very risky task. It is essential on presentation quality and the data warehouse that we can assure the information quality of the data quality. This last includes the multidimensional warehouse as it became the main tool for strategic model quality. In the last years different authors decisions [ENG99]. have proposed some useful guidelines to design Information quality of a data warehouse comprise data multidimensional models, however more objective warehouse system quality and data presentation quality indicators are needed to help designers and (see figure 1). In fact, it is very important that data in the managers to develop quality datawarehouses. In data warehouse reflects correctly the real world, but it is this paper a first proposal of metrics for also very important that data can be easily understood. In multidimensional model quality is shown together data warehouse system quality, as in an operational with their formal validation. database [PIA00], three different aspects could be considered: DBMSs quality, data model quality (both 1 Introduction conceptual and logical) and data quality. In order to assess DBMS quality we can use an Nowadays organizations can store vast amounts of data international standard like [ISO98], or some of the existing obtained at a relatively low cost, however these data fail to product comparative studies. This type of quality should provide information [GAR98]. To solve this problem, be addressed in the product selection stage of the data organizations are adopting a data warehouse, which is warehouse life cycle. defined as a “collection of subject-oriented, integrated, Data quality is composed by the data definition quality non-volatile data that supports the management decision (degree to which data definition accurately describes the meaning of the real-world entity type or fact-type that the The copyright of this paper belongs to the paper’s authors. Permission to data represents. Also meets the needs of all information copy without fee all or part of this material is granted provided that the customers to understand the data they use), the data copies are not made or distributed for direct commercial advantage. content quality (degree to which data values accurately Proceedings of the International Workshop on Design and represent the characteristics of the real-world entity or fact Management of Data Warehouses (DMDW'2001) and meet the need of the information costumers to perform Interlaken, Switzerland, June 4, 2001 their jobs effectively) and the data presentation quality (D. Theodoratos, J. Hammer, M. Jeusfeld, M. Staudt, eds.) (try to capture the degree in which the format presented is intuitive for the use to be made of the information) http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-39/ C. Calero, M. Piattini, C. Pascual, M.A. Serrano 2-1 [ENG98]. This kind of quality must address mostly in the Metrics could be used to build prediction systems for extraction, filtering, cleaning and cleansing, database projects, to understand and improve software synchronization, aggregation, loading, etc. activities of the development and maintenance projects, to maintain the life cycle. In the last years very interesting techniques quality of the systems, highlighting problematic areas, and have been proposed to assure data quality [BOU00]. to determine the best ways to help practitioners and researchers in their work. The final goal of our work is to define a set of metrics for assuring data warehouse quality by means of INFORMATION QUALITY measuring the dimensional data model quality. In the next section we will present the method we use for defining correct metrics. A first proposal of metrics for data DATAWAREHOUSE PRESENTATION warehouses will be described in section 3 and an example QUALITY QUALITY of the proposed metrics will be shown in section 4. Section 5 will present the formal validation of the metrics and conclusions and future work will come in the last section. DBMS DATA MODEL DATA QUALITY QUALITY QUALITY 2 Defining Valid Metrics Metrics definition must be done in a methodological way and it is necessary to follow a number of steps to ensure DIMENSIONAL PHYSICAL the reliability of the proposed metrics. Figure 2 presents MODEL QUALITY MODEL QUALITY the method we follow for the metrics proposal [CAL01]. Figure 1 Information and data warehouse quality METRIC DEFINITION Last, but not least, data warehouse model quality has a great influence in the overall information quality. The designer has to choose the physical tables, processes, indexes and data partitions, representing the logical data warehouse and facilitating its functionality [JAR00]. Two EMPIRICAL VALIDATION different aspects should be considered: dimensional data THEORETICAL VALIDATION model quality and physical data model quality. In fact EXPERIMENTS CASE STUDIES these two are often considered as different stages in the data warehouse life cycle. Dimensional data model is usually designed using the star schema modeling facility, which allows good response Figure 2. Steps followed in the definition and validation of times and an easy understanding of data and metadata for metrics both users and developers [KIM98]. Different techniques have also been researched for In this figure we have three main activities: optimizing physical data models [HAR96] [LAB97]. Our work focuses on dimensional data model quality. · Metrics definition. The first step is the proposal Different authors have suggested interesting of metrics. This definition is made taking into recommendations for achieving a “good” dimensional data account the specific characteristics of the system model [KIM98] [ADM98] [INM96]. However quality we want to measure and the experience of criteria are not enough on their own to ensure quality in designers of these systems. A goal-oriented practice, because different people will generally have approach, as GQM (Goal-Question-Metric) different interpretations of the same concept. According [BAS84] can also be very useful in this step. to the Total Quality Management (TQM) literature, · Theoretical validation. The second step is the measurable criteria for assessing quality are necessary to formal validation of the metrics. The formal avoid “arguments of style” [BOM97]. The objective validation helps us to know when and how apply should be to replace intuitive notions of design “quality” the metrics. There are two main tendencies in with formal, quantitative measures in order to reduce metrics validation: the frameworks based on subjectivity and bias in the evaluation process. However, axiomatic approaches [WEY88] [BRI96] [MOR97] for data modeling to progress from a “craft” to an and the ones based on the measurement theory engineering discipline, the desirable qualities of data [WIT97] [ZUS98]. The strength of measurement models need to be made explicit [LIN94]. A metric is away theory is the formulation of empirical conditions of measuring a quality factor in a consistent and objective from which we can derive hypothesis of reality. manner The final information when applying this kind of C. Calero, M. Piattini, C. Pascual, M.A. Serrano 2-2 frameworks in to know to which scale a metric NAFT(S) = NA(FT) + NFK(FT) pertains and based on this information we can Where FT is the fact table of the star S. know which statistics and which transformations can be done with the metric. · NA(S). Number of attributes of a star. · Empirical validation. The goal of this step is to prove the practical utility of the proposed NA(S) = NAFT(FT) + NADT(S) metrics. Although there are various ways of Where FT is the fact table of the star S. performing this step, basically we can divide the empirical validation into experimentation and case · NFK(S). Number of foreign keys of a star. studies [BAS99] [FEN97]. NDT As shown in figure 2, the process of defining and NFK(S) = NFK(FT) + å NFK(DTi) validating metrics is evolutionary and iterative. As a result i=1 of the feedback, metrics could be redefined based on Where FT is the fact table of the star S discarded theoretical or empirical validations. At the and Dti is the dimensional table number i of the star S moment, we have finished only a first iteration of metrics definition and theoretical validation for data warehouse · RSA(S). Ratio of star attributes. Quantity of the quality. number of attributes of dimension tables per This work only considers the two steps related with number of attributes of the fact table of the star. definition and formal validation. It is clear that these are only a first approach because it is fundamental to made NADT (S) empirical validation in order to prove which of all of the RSA(S) = proposed metrics are useful in the real world rejecting the NAFT(FT) ones that do not prove its uselfulness.
Recommended publications
  • EMC Greenplum Data Computing Appliance: High Performance for Data Warehousing and Business Intelligence an Architectural Overview
    EMC Greenplum Data Computing Appliance: High Performance for Data Warehousing and Business Intelligence An Architectural Overview EMC Information Infrastructure Solutions Abstract This white paper provides readers with an overall understanding of the EMC® Greenplum® Data Computing Appliance (DCA) architecture and its performance levels. It also describes how the DCA provides a scalable end-to- end data warehouse solution packaged within a manageable, self-contained data warehouse appliance that can be easily integrated into an existing data center. October 2010 Copyright © 2010 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com All other trademarks used herein are the property of their respective owners. Part number: H8039 EMC Greenplum Data Computing Appliance: High Performance for Data Warehousing and Business Intelligence—An Architectural Overview 2 Table of Contents Executive summary .................................................................................................
    [Show full text]
  • Microsoft's SQL Server Parallel Data Warehouse Provides
    Microsoft’s SQL Server Parallel Data Warehouse Provides High Performance and Great Value Published by: Value Prism Consulting Sponsored by: Microsoft Corporation Publish date: March 2013 Abstract: Data Warehouse appliances may be difficult to compare and contrast, given that the different preconfigured solutions come with a variety of available storage and other specifications. Value Prism Consulting, a management consulting firm, was engaged by Microsoft® Corporation to review several data warehouse solutions, to compare and contrast several offerings from a variety of vendors. The firm compared each appliance based on publicly-available price and specification data, and on a price-to-performance scale, Microsoft’s SQL Server 2012 Parallel Data Warehouse is the most cost-effective appliance. Disclaimer Every organization has unique considerations for economic analysis, and significant business investments should undergo a rigorous economic justification to comprehensively identify the full business impact of those investments. This analysis report is for informational purposes only. VALUE PRISM CONSULTING MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. ©2013 Value Prism Consulting, LLC. All rights reserved. Product names, logos, brands, and other trademarks featured or referred to within this report are the property of their respective trademark holders in the United States and/or other countries. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this report may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
    [Show full text]
  • Procurement and Spend Fact and Dimension Modeling
    Procurement and Spend Dimension and Fact Job Aid Contents Introduction .................................................................................................................................................. 2 Procurement and Spend – Purchase Orders Subject Area: ........................................................................ 10 Procurement and Spend – Purchase Requisitions Subject Area:................................................................ 14 Procurement and Spend – Purchase Receipts Subject Area:...................................................................... 17 1 Procurement and Spend Dimension and Fact Job Aid Introduction The purpose of this job aid is to provide an explanation of dimensional data modeling and of using dimensions and facts to build analyses within the Procurement and Spend Subject Areas. Dimensional Data Model The dimensional model is comprised of a fact table and many dimensional tables and used for calculating summarized data. Since Business Intelligence reports used in measuring the facts (aggregates) across various dimensions, dimensional data modeling is the preferred modeling technique in a BI environment. STARS - OBI data model based on Dimensional Modeling. The underlying database tables separated as Fact Tables and Dimension Tables. The dimension tables joined to fact tables with specific keys. This data model usually called Star Schema. The star schema separates business process data into facts, which hold the measurable, quantitative data about the business, and dimensions
    [Show full text]
  • Master Data Management (MDM) Improves Information Quality to Deliver Value
    MIT Information Quality Industry Symposium, July 15-17, 2009 Master Data Management (MDM) Improves Information Quality to Deliver Value ABSTRACT Master Data Management (MDM) reasserts IT’s role in responsibly managing business-critical information—master data—to reasonable quality and reliability standards. Master data includes information about products, customers, suppliers, locations, codes, and other critical business data. For most commercial businesses, governmental, and non-governmental organizations, master data is in a deplorable state. This is true although MDM is not new—it was, is, and will be IT’s job to remediate and control. Poor-quality master data is an unfunded enterprise liability. Bad data reduces the effectiveness of product promotions; it causes unnecessary confusion throughout the organization; it misleads corporate officers, regulators and shareholders; and it dramatically increases the IT cost burden with ceaseless and fruitless spending for incomplete error remediation projects. This presentation describes—with examples—why senior IT management should launch an MDM process, what governance they should institute for master data, and how they can build cost-effective MDM solutions for the enterprises they serve. BIOGRAPHY Joe Bugajski Senior Analyst Burton Group Joe Bugajski is a senior analyst for Burton Group. He covers IT governance, architecture, and data – governance, management, standards, access, quality, and integration. Prior to Burton Group, Joe was chief data officer at Visa responsible worldwide for information interoperability. He also served as Visa’s chief enterprise architect and resident entrepreneur covering risk systems and business intelligence. Prior to Visa, Joe was CEO of Triada, a business intelligence software provider. Before Triada, Joe managed engineering information systems for Ford Motor Company.
    [Show full text]
  • Measuring Data Warehouse Return on Investment
    Measuring Data Warehouse Return on Investment A Whitepaper by Sid Adelman Executive Summary Introduction Section 1: Data Warehouse Costs 1.1 Cost Estimates as Part of Cost Justification 1.2 Costs 1.3 Total Cost of Ownership 1.4 Post-Implementation Cost Measurement Section 2: Benefits 2.1 Estimating Tangible Benefits 2.2 Estimating Intangible Benefits 2.3 Post Implementation Benefits Measurement Section 3: Full Cycle Assessment of Value Appendix A – ROI Calculation Process ROI Example Cost of Capital Risk Net Present Value Internal Rate of Return Payback Period Appendix B - Cost Calculation Template Appendix C - Benefits Calculation Templates Appendix D – Glossary References Executive Summary Management wants to know the business value of the data warehouse, measured in quantitative terms, with the metrics in the form of return on investment (ROI). ROI refers to a few different ways of calculating the value of an investment which can be calculated by payback period (break-even analysis), net present value, or rate of return (yield). Cost justification - Many data warehouse projects were implemented without knowing how much they would cost. Many were authorized without even estimating the potential benefits. However, ROI should become part of normal cost justification and should also be part of evaluating the system once its up and running. Without an ROI process, the organization may lose business value because the wrong project was implemented. Data warehouse costs – The costs for the data warehouse can be substantial including hardware, software, internal personnel costs, consultants and contractors, network, training for both IT and the business users, help desk, and operations and system administration.
    [Show full text]
  • Benchmarking Bitemporal Database Systems: Ready for the Future Or Stuck in the Past?
    Benchmarking Bitemporal Database Systems: Ready for the Future or Stuck in the Past? Martin Kaufmann†§, Peter M. Fischer#, Norman May§, Donald Kossmann† †Systems Group #Albert-Ludwigs-Universität §SAP AG ETH Zürich, Switzerland Freiburg, Germany Walldorf, Germany {martinka,donaldk} peter.fi[email protected] [email protected] @inf.ethz.ch freiburg.de ABSTRACT tremendous possibility for improved performance. As database After more than a decade of a virtual standstill, the adoption of vendors now provide implementations of such temporal data and temporal data management features has recently picked up speed, operators, a natural question is how well they actually perform for driven by customer demand and the inclusion of temporal expres- typical temporal workloads. sions into SQL:2011. Most of the big commercial DBMS now Since no generally accepted workload for the evaluation of tem- include support for bitemporal data and operators. In this paper, we poral DBMS exists, we developed a comprehensive benchmark perform a thorough analysis of these commercial temporal DBMS: proposal and presented it at TPCTC 2013 [11]. This benchmark We investigate their architecture, determine their performance and extends the TPC-H schema with a temporal component, provides study the impact of performance tuning. This analysis utilizes a definition of updates with well-defined data evolution as well our recent (TPCTC 2013) benchmark proposal, which includes a as a wide range of synthetic and application-oriented queries. It comprehensive temporal workload definition. The results of our therefore allows us to examine the functional coverage as well as analysis show that the support for temporal data is still in its in- the performance of different databases regarding temporal features.
    [Show full text]
  • Data Warehouse and OLAP
    Data Warehouse and OLAP Week 5 1 Midterm I • Friday, March 4 • Scope – Homework assignments 1 – 4 – Open book Team Homework Assignment #7 • RdRead pp. 121 – 139, 146 – 150 of the text bkbook. • Do Examples 3.8, 3.10 and Exercise 3.4 (b) and (c). Prepare for the results of the homework assignment. • Due date – beginning of the lecture on Friday March11th. Topics • Definition of data warehouse • Multidimensional data model • Data warehouse architecture • From data warehousing to data mining What is Data Warehouse ?(1)? (1) • A data warehouse is a repository of information collected from multiple sources, stored under a unified schema, and that usually resides at a single site • A data warehouse is a semantically consistent data store that serves as a physical implementation of a decision support data model and stores the information on which an enterprise need to make strategic decisions What is Data Warehouse? (2) • Data warehouses provide on‐line analytical processing (OLAP) tools for the interactive analysis of multidimensional data of varied granularities, which facilitate effective data generalization and data mining • Many other data mining functions, such as association, classification, prediction, and clustering, can be itintegra tdted with OLAP operations to enhance interactive mining of knowledge at multiple levels of abstraction What is Data Warehouse? (3) • A decision support database that is maintained separately from the organization’s operational database • “A data warehouse is a subject‐oriented, integrated, time‐variant, and nonvolatile collection of data in support of management’s decision‐making process [Inm96].”—W. H. Inmon Data Warehouse Framework data mining Figure 1.7 Typical framework of a data warehouse for AllElectronics 8 Data Warehouse is SbjSubject-OiOriente d • Organized around major subjects, such as customer, product, sales, etc.
    [Show full text]
  • Extract Transform Load Data with ETL Tools
    Volume 7, No. 3, May-June 2016 International Journal of Advanced Research in Computer Science REVIEW ARTICLE Available Online at www.ijarcs.info Extract Transform Load Data with ETL Tools Preeti Dhanda Neetu Sharma M.Tech,Computer Science Engineering, (HOD C.S.E dept.) Ganga Institute of Technology and Ganga Institute of Technology and Management 20 KM,Bahadurgarh- Management 20 KM,Bahadurgarh- Jhajjar Road, Kablana, Dist-Jhajjar, Jhajjar Road, Kablana, Dist-Jhajjar, Haryana, India Haryana, India Abstract: As we all know business intelligence (BI) is considered to have an extraordinary impact on businesses. Research activity has grown in the last years. A significant part of BI systems is a well performing Implementation of the Extract, Transform, and Load (ETL) process. In typical BI projects, implementing the ETL process can be the task with the greatest effort. Here, set of generic Meta model constructs with a palette of regularly used ETL activities, is specialized, which are called templates. Keywords: ETL tools, transform, data, business, intelligence INTRODUCTION Loading: Now, the real loading of data into the data warehouse has to be done. The early Load which generally We all want to load our data warehouse regularly so that it is not time-critical is great from the Incremental Load. can assist its purpose of facilitating business analysis[1]. To Whereas the first phase affected productive systems, loading do this, data from one or more operational systems desires to can have an giant effect on the data warehouse. This be extracted and copied into the warehouse. The process of especially has to be taken into consideration with regard to extracting data from source systems and carrying it into the the complex task of updating currently stored data sets.
    [Show full text]
  • METL: Managing and Integrating ETL Processes
    METL: Managing and Integrating ETL Processes Alexander Albrecht supervised by Felix Naumann Hasso-Plattner-Institute at the University of Potsdam, Germany {albrecht,naumann}@hpi.uni-potsdam.de ABSTRACT Etl processes cover two typical scenarios in the context of data warehouse loading: Augmenting data with additional Companies use Extract-Transform-Load (Etl) tools to save time and costs when developing and maintaining data migra- information and fact loading. The Etl processes were im- plemented with IBM InfoSphere DataStage, the Etl com- tion tasks. Etl tools allow the definition of often complex 1 processes to extract, transform, and load heterogeneous data ponent of the IBM Information Server . The Etl process into a data warehouse or to perform other data migration in Figure 1 loads daily sales data of a retail company from an server into a database table. Raw sales data consist tasks. In larger organizations many Etl processes of dif- Ftp ferent data integration and warehouse projects accumulate. of sales volume grouped by product key and shop number. Such processes encompass common sub-processes, shared At the beginning, data is augmented with additional shop data sources and targets, and same or similar operations. information, such as shop address and the sales district key, However, there is no common method or approach to sys- using a join transformation over the shop number. Because there are some shops with a missing sales district key, this lo- tematically manage large collections of Etl processes. With cation information is subsequently consolidated: The data Metl (Managing Etl) we present an Etl management ap- flow is split into two streams of tuples – one stream with proach that supports high-level Etl management.
    [Show full text]
  • Implementation Aspects of Bitemporal Databases
    VILNIUS UNIVERSITY FACULTY OF MATHEMATICS AND INFORMATICS DEPARTMENT OF COMPUTER SCIENCE II Master Thesis Implementation Aspects of Bitemporal Databases Done by: Dmitrij Biriukov signature Supervisor: dr. Linas Bukauskas Vilnius 2018 Contents Abstract 4 Santrauka 5 Introduction 6 1 Related work 7 1.1 Time dimensions . .7 1.1.1 Valid time . .7 1.1.2 Transaction time . .7 1.2 Bitemporal entity . .8 1.3 Bitemporal data types . .8 1.4 Data definition principles . .9 1.5 Data flow . 10 2 Relational databases 11 2.1 Database engine . 11 3 NoSQL databases 12 3.1 What is NoSQL? . 12 3.2 Key-value store . 12 3.3 Document-oriented database systems . 13 3.4 Graph-oriented databases . 14 3.5 Object-oriented database management systems . 14 3.6 Column-oriented databases . 15 3.7 NoSQL database type comparison . 16 4 NoSQL properties 17 4.1 Schema-less model . 17 4.2 Big Data support . 17 4.3 Database scaling concepts . 18 4.3.1 Scale-out . 18 4.3.2 Scale-up . 18 4.4 CAP Theorem . 19 4.4.1 Consistency . 19 4.4.2 Availability . 20 4.4.3 Partition Tolerance . 20 5 Goal and objectives 21 6 Model 22 6.1 Extending database . 22 6.2 Bitemporal operations . 22 6.3 Comparison of time . 22 6.4 Coalescing . 23 6.5 Vertical slice . 23 2 6.6 Horizontal slice . 24 6.7 Bitemporal slice . 25 6.8 Data definition . 27 6.9 Output data association . 27 6.10 Association algorithm . 28 7 Implementation 30 7.1 Application architecture .
    [Show full text]
  • Database Benchmarking for Supporting Real-Time Interactive
    Database Benchmarking for Supporting Real-Time Interactive Querying of Large Data Leilani Battle, Philipp Eichmann, Marco Angelini, Tiziana Catarci, Giuseppe Santucci, Yukun Zheng, Carsten Binnig, Jean-Daniel Fekete, Dominik Moritz To cite this version: Leilani Battle, Philipp Eichmann, Marco Angelini, Tiziana Catarci, Giuseppe Santucci, et al.. Database Benchmarking for Supporting Real-Time Interactive Querying of Large Data. SIGMOD ’20 - International Conference on Management of Data, Jun 2020, Portland, OR, United States. pp.1571-1587, 10.1145/3318464.3389732. hal-02556400 HAL Id: hal-02556400 https://hal.inria.fr/hal-02556400 Submitted on 28 Apr 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Database Benchmarking for Supporting Real-Time Interactive Querying of Large Data Leilani Battle Philipp Eichmann Marco Angelini University of Maryland∗ Brown University University of Rome “La Sapienza”∗∗ College Park, Maryland Providence, Rhode Island Rome, Italy [email protected] [email protected] [email protected] Tiziana Catarci Giuseppe Santucci Yukun Zheng University of Rome “La Sapienza”∗∗ University of Rome “La Sapienza”∗∗ University of Maryland∗ [email protected] [email protected] [email protected] Carsten Binnig Jean-Daniel Fekete Dominik Moritz Technical University of Darmstadt Inria, Univ.
    [Show full text]
  • Data Quality: the First Step on the Path to Master Data Management
    Data Quality: the First Step on the Path to Master Data Management SOLUTION BRIEF This document contains Confi dential, Proprietary and Trade Secret Information (“Confi dential Information”) of Informatica Corporation and may not be copied, distributed, duplicated, or otherwise reproduced in any manner without the prior written consent of Informatica. While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Informatica does not accept responsibility for any kind of loss resulting from the use of information contained in this document. The information contained in this document is subject to change without notice. The incorporation of the product attributes discussed in these materials into any release or upgrade of any Informatica software product—as well as the timing of any such release or upgrade—is at the sole discretion of Informatica. Protected by one or more of the following U.S. Patents: 6,032,158; 5,794,246; 6,014,670; 6,339,775; 6,044,374; 6,208,990; 6,208,990; 6,850,947; 6,895,471; or by the following pending U.S. Patents: 09/644,280; 10/966,046; 10/727,700. This edition published June 2007 Solution Brief Table of Contents Executive Summary . .2 Initiate MDM by First Establishing Data Quality Baseline. .4 Profi ling Reduces MDM Implementation Risks . .4 Business-Relevant Data Quality Metrics . .5 Completeness. 6 Conformity . 6 Consistency . 6 Fostering a Data Quality Culture . .7 Summary: For MDM Start with Data Quality . .9 Informatica Underpins MDM. .9 Informatica Products .
    [Show full text]