DOCSLIB.ORG

Managing Current and Historical View of Information in a Data Warehouse Environment

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Managing Current and Historical View of Information in a Data Warehouse Environment Managing Current and Historical view of Information in a Data Warehouse Environment By Nagarajan Subramanian e-mail:[email protected] TABLE OF CONTENTS Managing Current and Historical view of Information in a Data warehouse environment.................................................................................................. 3 Introduction............................................................................................... 3 Current and Historical view .......................................................................... 3 Traditional DW approach.............................................................................. 4 Type 2 (Slowly Changing Dimension – SCD)........................................ 4 Type 3 (Slowly Changing Dimension – SCD)........................................ 4 Type 2 + (SCD 2+) ......................................................................... 5 Other DW solutions ......................................................................... 6 A relook at Surrogate key – Modified Surrogate key approach ........................... 6 Summary .................................................................................................. 7 Managing Current and Historical view of Information in a Data Warehouse environment Introduction In today’s challenging business environment, the core strength of data warehousing is to be utilized to its maximum to achieve long-term customer satisfaction. Access to faster and accurate information resulting in smarter decision is the key to success. Business executives today understand that access to such information provides competitive advantage. Data warehouse is one single place to do multi-point analysis and to derive a completely different perspective of business to enhance the customer satisfaction program. Looking into the Information from both current view and historical view of business is a key factor in understanding the trends of customer business relationship. In this article, I have tried to present the various data warehouse design aspects to consider for providing both the current and historical view of data. Current and Historical view Consider a business scenario where Dilbert International acquired Alice Corporation in 2007 to become Albert International. In 2008, Albert International goes public to become Albert Corporation. If after the successful transformations, a three year profitability historical view report of Albert Corporation would require facts to be broken down to show Dilbert International’s, Albert International’s and Albert Corporation’s profitability. But a current perspective of the profitability report would require ignoring the acquisition and reporting it as if the Albert Corporation was in business prior 2008. Below is a sample display of how the profitability report would look like in historical and current view. Historical view Fiscal Year Company Profit after tax (billions) 2006 Dilbert International US $ 10 2007 Albert International US $ 15 2008 Albert Corporation US $ 20 Current view Fiscal Year Company Profit after tax (billions) 2006 Albert Corporation US $ 10 2007 Albert Corporation US $ 15 2008 Albert Corporation US $ 20 Traditional DW approach Traditional DW methods suggest lot of techniques to handle this particular scenario. Some of them are listed below. Type 2 (Slowly Changing Dimension – SCD) This method uses a surrogate key that is generated in the DW to keep track of changes to the dimension. By this method, every time a change is encountered in the source system dimension, a new record is inserted into the dimension table. Fact table starts using the new surrogate key to identify the correct dimension record there by making historical reporting very simple. For e.g., in our business scenario, the dimension table and fact table records would look similar to the example given below. Dimension table Surrogate Key Period Begin Period End Company Name date date 1 2006-01-01 2006-12-31 Dilbert International 2 2007-01-01 2007-12-31 Albert International 3 2008-01-01 - Albert Corporation Fact table Surrogate Key Period Ending Profit (in Billions) 1 2006-12-31 US $ 10 2 2007-12-31 US $ 15 3 2008-12-31 US $ 20 This approach simplifies the historical reporting, but makes the current view of reporting complex. The current view of the data can be achieved through complex SQL constructs or multi-join. But when the scenario includes reporting for multiple corporations and its acquisitions, the data handling becomes very complex to implement. This is because there is no relation between the companies maintained in the dimension table. Type 3 (Slowly Changing Dimension – SCD) Type 3 approach works similar to type 2 but differs in the basic handling of dimension data. Type 3 suggests keeping multiple columns in the dimension table to handle changes to the dimension table. That is, it suggests keeping multiple columns for dimension attributes. When one of the attribute value changes, the old value is moved to a separate column and the current column is updated with the new value. For e.g, Dimension table Surrogate Key Company Name Company Name Company Name Period 1 Period 2 Period 3 1 Dilbert Albert International Albert Corporation International Fact table Surrogate Key Period Profit (in Billions) 1 2006 US $ 10 1 2007 US $ 15 1 2008 US $ 20 In the above example, the historical changes for the company name are stored in multiple columns with each column representing the name of the company at different periods. So, the reporting system needs to take care of identifying the correct company name based on the periods. This is a pretty simple approach but becomes cumbersome when there are multiple such changes and when you don’t have a definite number of changes to handle. Another version of type 3 suggests keeping the number of columns constant based on the requirement to see number of versions and recycle the column data whenever the number of changes crosses the number of columns. This not only results in loss of history but defeats the basic purpose of historical reporting. Type 2 + (SCD 2+) A slight variation of SCD 2 suggests maintaining two separate tables of dimension. One table would hold the historical changes and the other will maintain the current dimension data as illustrated below Historical Dimension table Surrogate Key Period Begin Period End Company Name date date 1 2006-01-01 2006-12-31 Dilbert International 2 2007-01-01 2007-12-31 Albert International 3 2008-01-01 - Albert Corporation Current Dimension table Surrogate Key Period Begin Period End Company Name date date 1 2006-01-01 2006-12-31 Albert Corporation 2 2007-01-01 2007-12-31 Albert Corporation 3 2008-01-01 - Albert Corporation Fact table Surrogate Key Period Ending Profit (in Billions) 1 2006-12-31 US $ 10 2 2007-12-31 US $ 15 3 2008-12-31 US $ 20 In the above example, when the fact table is joined to “historical dimension table”, we get the history view of the data and when it is joined to “current dimension table”, we get the current view of the data. This is again a very simple approach where the dimension table is duplicated and based on the requirement to see history vs. current data, the joins are performed. The main disadvantage of this approach is the duplication of dimension table where the current table actually stores data that is not true. The other disadvantage of this approach is that these two tables must be kept in sync by the ETL processes which makes it complicated. Other DW solutions There are other fact based approaches for this problem. Maintaining both current and historical surrogate keys in the fact table is one such approach. This is a complicated ETL approach where both the keys are maintained in the fact table as two separate columns. Based on the requirements, the correct column is joined to the dimension table to get both historical and current reporting. A relook at Surrogate key – Modified Surrogate key approach While there are still debates over the requirement of a surrogate key in data warehouses, the following solution can be implemented by relooking the way surrogate key is handled in a dimension table to handle the above discussed business scenario. The basic characteristic of a surrogate key is that “it is a unique key to identify a unique row in a dimension table”. The solution described below changes this characteristic and starts reusing surrogate keys for the related dimension values along with the traditional SCD 2 approach to handle the above discussed business scenario. In addition to this, we shall also add an indicator column to our dimension table to identify the current record. For e.g, Dimension table Surrogate Period Period End Company Name Current Key Begin date date record Indicator 1 2006-01-01 2006-12-31 Dilbert International N 1 2007-01-01 2007-12-31 Albert International N 1 2008-01-01 - Albert Corporation Y Fact table Surrogate Key Period Ending Profit (in Billions) 1 2006-12-31 US $ 10 1 2007-12-31 US $ 15 1 2008-12-31 US $ 20 The fact table is joined to the dimension table in two different ways based on the reporting requirements. For historical reporting, the “period ending” of the fact table is joined to the dimension table’s “Period begin date” and “Period end date” using a between clause in addition to the surrogate key join. For current reporting, the condition “current record indicator”=“Y” is added to the condition and the fact table is joined to the dimension table based on the surrogate key. There are advantages and disadvantages in this approach just
Load more

Recommended publications
  • Cubes Documentation Release 1.0.1
    Cubes Documentation Release 1.0.1 Stefan Urbanek April 07, 2015 Contents 1 Getting Started 3 1.1 Introduction.............................................3 1.2 Installation..............................................5 1.3 Tutorial................................................6 1.4 Credits................................................9 2 Data Modeling 11 2.1 Logical Model and Metadata..................................... 11 2.2 Schemas and Models......................................... 25 2.3 Localization............................................. 38 3 Aggregation, Slicing and Dicing 41 3.1 Slicing and Dicing.......................................... 41 3.2 Data Formatters........................................... 45 4 Analytical Workspace 47 4.1 Analytical Workspace........................................ 47 4.2 Authorization and Authentication.................................. 49 4.3 Configuration............................................. 50 5 Slicer Server and Tool 57 5.1 OLAP Server............................................. 57 5.2 Server Deployment.......................................... 70 5.3 slicer - Command Line Tool..................................... 71 6 Backends 77 6.1 SQL Backend............................................. 77 6.2 MongoDB Backend......................................... 89 6.3 Google Analytics Backend...................................... 90 6.4 Mixpanel Backend.......................................... 92 6.5 Slicer Server............................................. 94 7 Recipes 97 7.1 Recipes...............................................
    [Show full text]
  • Business Intelligence and Column-Oriented Databases
    Central____________________________________________________________________________________________________ European Conference on Information and Intelligent Systems Page 12 of 344 Business Intelligence and Column-Oriented Databases Kornelije Rabuzin Nikola Modrušan Faculty of Organization and Informatics NTH Mobile, University of Zagreb Međimurska 28, 42000 Varaždin, Croatia Pavlinska 2, 42000 Varaždin, Croatia [email protected] [email protected] Abstract. In recent years, NoSQL databases are popular document-oriented database systems is becoming more and more popular. We distinguish MongoDB. several different types of such databases and column- oriented databases are very important in this context, for sure. The purpose of this paper is to see how column-oriented databases can be used for data warehousing purposes and what the benefits of such an approach are. HBase as a data management Figure 1. JSON object [15] system is used to store the data warehouse in a column-oriented format. Furthermore, we discuss Graph databases, on the other hand, rely on some how star schema can be modelled in HBase. segment of the graph theory. They are good to Moreover, we test the performances that such a represent nodes (entities) and relationships among solution can provide and we compare them to them. This is especially suitable to analyze social relational database management system Microsoft networks and some other scenarios. SQL Server. Key value databases are important as well for a certain key you store (assign) a certain value. Keywords. Business Intelligence, Data Warehouse, Document-oriented databases can be treated as key Column-Oriented Database, Big Data, NoSQL value as long as you know the document id. Here we skip the details as it would take too much time to discuss different systems [21].
    [Show full text]
  • CDW: a Conceptual Overview 2017
    CDW: A Conceptual Overview 2017 by Margaret Gonsoulin, PhD March 29, 2017 Thanks to: • Richard Pham, BISL/CDW for his mentorship • Heidi Scheuter and Hira Khan for organizing this session 3 Poll #1: Your CDW experience • How would you describe your level of experience with CDW data? ▫ 1- Not worked with it at all ▫ 2 ▫ 3 ▫ 4 ▫ 5- Very experienced with CDW data Agenda for Today • Get to the bottom of all of those acronyms! • Learn to think in “relational data” terms • Become familiar with the components of CDW ▫ Production and Raw Domains ▫ Fact and Dimension tables/views • Understand how to create an analytic dataset ▫ Primary and Foreign Keys ▫ Joining tables/views Agenda for Today • Get to the bottom of all of those acronyms! • Learn to think in “relational data” terms • Become familiar with the components of CDW ▫ Production and Raw Domains ▫ Fact and Dimension tables/views • Creating an analytic dataset ▫ Primary and Foreign Keys ▫ Joining tables/views “C”DW, “R”DW & “V”DW • Users will see documentation referring to xDW. • The “x” is a variable waiting to be filled in with either: ▫ “V” for VISN, ▫ “R” for region or ▫ “C” for corporate (meaning “national VHA”) • Each organizational level of the VA has its own data warehouse focusing on its own population. • This talk focuses on CDW only. 7 Flow of data into the warehouse VistA = Veterans Health Information Systems and Technology Architecture C“DW” • The “DW” in CDW stands for “Data Warehouse.” • Data Warehouse = a data delivery system intended to give users the information they need to support their business decisions.
    [Show full text]
  • Building an Effective Data Warehousing for Financial Sector
    Automatic Control and Information Sciences, 2017, Vol. 3, No. 1, 16-25 Available online at http://pubs.sciepub.com/acis/3/1/4 ©Science and Education Publishing DOI:10.12691/acis-3-1-4 Building an Effective Data Warehousing for Financial Sector José Ferreira1, Fernando Almeida2, José Monteiro1,* 1Higher Polytechnic Institute of Gaya, V.N.Gaia, Portugal 2Faculty of Engineering of Oporto University, INESC TEC, Porto, Portugal *Corresponding author: [email protected] Abstract This article presents the implementation process of a Data Warehouse and a multidimensional analysis of business data for a holding company in the financial sector. The goal is to create a business intelligence system that, in a simple, quick but also versatile way, allows the access to updated, aggregated, real and/or projected information, regarding bank account balances. The established system extracts and processes the operational database information which supports cash management information by using Integration Services and Analysis Services tools from Microsoft SQL Server. The end-user interface is a pivot table, properly arranged to explore the information available by the produced cube. The results have shown that the adoption of online analytical processing cubes offers better performance and provides a more automated and robust process to analyze current and provisional aggregated financial data balances compared to the current process based on static reports built from transactional databases. Keywords: data warehouse, OLAP cube, data analysis, information system, business intelligence, pivot tables Cite This Article: José Ferreira, Fernando Almeida, and José Monteiro, “Building an Effective Data Warehousing for Financial Sector.” Automatic Control and Information Sciences, vol.
    [Show full text]
  • Integrating Compression and Execution in Column-Oriented Database Systems
    Integrating Compression and Execution in Column-Oriented Database Systems Daniel J. Abadi Samuel R. Madden Miguel C. Ferreira MIT MIT MIT [email protected] [email protected] [email protected] ABSTRACT commercial arena [21, 1, 19], we believe the time is right to Column-oriented database system architectures invite a re- systematically revisit the topic of compression in the context evaluation of how and when data in databases is compressed. of these systems, particularly given that one of the oft-cited Storing data in a column-oriented fashion greatly increases advantages of column-stores is their compressibility. the similarity of adjacent records on disk and thus opportuni- Storing data in columns presents a number of opportuni- ties for compression. The ability to compress many adjacent ties for improved performance from compression algorithms tuples at once lowers the per-tuple cost of compression, both when compared to row-oriented architectures. In a column- in terms of CPU and space overheads. oriented database, compression schemes that encode multi- In this paper, we discuss how we extended C-Store (a ple values at once are natural. In a row-oriented database, column-oriented DBMS) with a compression sub-system. We such schemes do not work as well because an attribute is show how compression schemes not traditionally used in row- stored as a part of an entire tuple, so combining the same oriented DBMSs can be applied to column-oriented systems. attribute from different tuples together into one value would We then evaluate a set of compression schemes and show that require some way to \mix" tuples.
    [Show full text]
  • Column-Stores Vs. Row-Stores: How Different Are They Really?
    Column-Stores vs. Row-Stores: How Different Are They Really? Daniel J. Abadi Samuel R. Madden Nabil Hachem Yale University MIT AvantGarde Consulting, LLC New Haven, CT, USA Cambridge, MA, USA Shrewsbury, MA, USA [email protected] [email protected] [email protected] ABSTRACT General Terms There has been a significant amount of excitement and recent work Experimentation, Performance, Measurement on column-oriented database systems (“column-stores”). These database systems have been shown to perform more than an or- Keywords der of magnitude better than traditional row-oriented database sys- tems (“row-stores”) on analytical workloads such as those found in C-Store, column-store, column-oriented DBMS, invisible join, com- data warehouses, decision support, and business intelligence appli- pression, tuple reconstruction, tuple materialization. cations. The elevator pitch behind this performance difference is straightforward: column-stores are more I/O efficient for read-only 1. INTRODUCTION queries since they only have to read from disk (or from memory) Recent years have seen the introduction of a number of column- those attributes accessed by a query. oriented database systems, including MonetDB [9, 10] and C-Store [22]. This simplistic view leads to the assumption that one can ob- The authors of these systems claim that their approach offers order- tain the performance benefits of a column-store using a row-store: of-magnitude gains on certain workloads, particularly on read-intensive either by vertically partitioning the schema, or by indexing every analytical processing workloads, such as those encountered in data column so that columns can be accessed independently. In this pa- warehouses.
    [Show full text]
  • Using Online Analytical Processing (OLAP) in Data Warehousing
    International Journal of Science and Research (IJSR) ISSN (Online): 2319-7064 Index Copernicus Value (2013): 6.14 | Impact Factor (2013): 4.438 Using Online Analytical Processing (OLAP) in Data Warehousing Mohieldin Mahmoud1, Alameen Eltoum2, Ramadan Faraj3 1, 2, 3al Asmarya Islamic University Abstract: Data warehousing is needed in recent time to give information that helps in the development of a company, support decision makers, it provides an efficient ways for transforming, manipulating analyzing large amount of data from different organizations or companies. In this paper we aimed to over view, data warehousing definition; how data are gathered from multi sources in to data warehousing using a model. Important techniques were shown; how to analyze data using data warehousing, to make decisions, this technique called: Online Analytical Processing OLAP. Keywords: Data Warehousing, OLAP, gathering, data cleansing, OLAP FASMI Test. 1. Introduction Enhances Data Quality and Consistency, Provides Historical data And Generates a High ROI. The concept of data warehousing returns back to the early 1980s, where was considered relational database 3. Gathering Data From Multi Source management systems. A data warehouse is a destination (archive) of information gathered from many sources, kept The data sources send new information in to warehouse, under a unified schema, at a single site. either continuously or periodically where data warehouse periodically requests new information from data sources then The businesses of all sizes its realized the importance of data keeping warehouse exactly synchronized from data sources warehouse, because there are significant benefits by but that is too expensive, and acts on data updates are implementing a Data warehouse.
    [Show full text]
  • Columnar Storage in SQL Server 2012
    Columnar Storage in SQL Server 2012 Per-Ake Larson Eric N. Hanson Susan L. Price [email protected] [email protected] [email protected] Abstract SQL Server 2012 introduces a new index type called a column store index and new query operators that efficiently process batches of rows at a time. These two features together greatly improve the performance of typical data warehouse queries, in some cases by two orders of magnitude. This paper outlines the design of column store indexes and batch-mode processing and summarizes the key benefits this technology provides to customers. It also highlights some early customer experiences and feedback and briefly discusses future enhancements for column store indexes. 1 Introduction SQL Server is a general-purpose database system that traditionally stores data in row format. To improve performance on data warehousing queries, SQL Server 2012 adds columnar storage and efficient batch-at-a- time processing to the system. Columnar storage is exposed as a new index type: a column store index. In other words, in SQL Server 2012 an index can be stored either row-wise in a B-tree or column-wise in a column store index. SQL Server column store indexes are “pure” column stores, not a hybrid, because different columns are stored on entirely separate pages. This improves I/O performance and makes more efficient use of memory. Column store indexes are fully integrated into the system. To improve performance of typical data warehous- ing queries, all a user needs to do is build a column store index on the fact tables in the data warehouse.
    [Show full text]
  • Virtual Denormalization Via Array Index Reference for Main Memory OLAP
    IEEE TRANSACTIONS ON KNOWLEDGE AND DATA ENGINEERING, VOL. 27, NO. X, XXXXX 2015 1 Virtual Denormalization via Array Index Reference for Main Memory OLAP Yansong Zhang, Xuan Zhou, Ying Zhang, Yu Zhang, Mingchuan Su, and Shan Wang Abstract—Denormalization is a common tactic for enhancing performance of data warehouses, though its side-effect is quite obvious. Besides being confronted with update abnormality, denormalization has to consume additional storage space. As a result, this tactic is rarely used in main memory databases, which regards storage space, i.e., RAM, as scarce resource. Nevertheless, our research reveals that main memory database can benefit enormously from denormalization, as it is able to remarkably simplify the query processing plans and reduce the computation cost. In this paper, we present A-Store, a main memory OLAP engine customized for star/snowflake schemas. Instead of generating fully materialized denormalization, A-Store resorts to virtual denormalization by treating array indexes as primary keys. This design allows us to harvest the benefit of denormalization without sacrificing additional RAM space. A-Store uses a generic query processing model for all SPJGA queries. It applies a number of state-of-the-art optimization methods, such as vectorized scan and aggregation, to achieve superior performance. Our experiments show that A-Store outperforms the most prestigious MMDB systems significantly in star/snowflake schema based query processing. Index Terms—Main-memory, OLAP, denormalization, A-Store, array index. Ç 1INTRODUCTION HE purpose of database normalization is to eliminate strategy of denormalization. Recent development of MMDB Tdata redundancy, so as to save storage space and avoid [1], [2], [3] has shown that simplicity of data processing update abnormality.
    [Show full text]
  • Splitting Facts Using Weights
    SPLITTING FACTS USING WEIGHTS Liga Grundmane, Laila Niedrite University of Latvia, Department of Computer Science, 19 Raina blvd., Riga, Latvia Keywords: Data Warehouse, Weights, Fact Granularity. Abstract: A typical data warehouse report is the dynamic representation of some objects’ behaviour or changes of objects’ properties. If this behaviour is changing, it is difficult to make such reports in an easy way. It is possible to use the fact splitting to make this task simpler and more comprehensible for users. In the presented paper two solutions of splitting facts by using weights are described. One of the possible solutions is to make the proportional weighting accordingly to splitted record set size. It is possible to take into account the length of the fact validity time period and the validity time for each splitted fact record. 1 INTRODUCTION one set have to be 100 percent. There exists an opinion that bridge tables are not easily Following the classical data warehouse theory understandable for users, however such a modeling (Kimball, 1996), (Inmon, 1996) there are fact tables technique satisfies business requirements quite good. and dimension tables in the data warehouse. If a data mart exists with only aggregated values, Measures about the objects of interest of business it is not possible to get the exact initial values. It is analysts are stored in the fact table. This information possible to get only some approximation. So if we is usually represented as different numbers. At the need to lower the fact table grain, we have to split same time the information about properties of these the aggregated fact value accordingly to the chosen objects is stored in the dimensions.
    [Show full text]
  • Automated Presentation of Slowly Changing Dimensions
    IT 09 025 Examensarbete 30 hp Juni 2009 Automated presentation of slowly changing dimensions Christer Boedeker Institutionen för informationsteknologi Department of Information Technology Abstract Automated presentation of slowly changing dimensions Christer Boedeker Teknisk- naturvetenskaplig fakultet UTH-enheten On the subject of data warehousing, a lot of material is available on what needs to be done to maintain a presentation area, but very little on how to do it. This paper Besöksadress: presents a structure and process for automatically maintaining and updating a Ångströmlaboratoriet Lägerhyddsvägen 1 multidimensional presentation area from a fully normalized data staging area. The Hus 4, Plan 0 paper also discusses a theoretical algorithm for finding the best division of slowly changing dimension attributes into several groups based on how they change Postadress: together. Box 536 751 21 Uppsala Telefon: 018 – 471 30 03 Telefax: 018 – 471 30 00 Hemsida: http://www.teknat.uu.se/student Handledare: Andreas Perjus Ämnesgranskare: Tore Risch Examinator: Anders Jansson IT 09 025 Tryckt av: Reprocentralen ITC Contents 1. Abstract ........................................................................................................................................ 3 2. Introduction .................................................................................................................................. 7 3. Background ..................................................................................................................................
    [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]