DOCSLIB.ORG

Chapter 4: Data Warehousing and On-Line Analytical Processing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Chapter 4: Data Warehousing and On-line Analytical Data Warehousing Processing & Data Warehouse: Basic Concepts On-Line Analytical Processing Data Warehouse Modeling: Data Cube and OLAP Erwin M. Bakker & Stefan Manegold Data Warehouse Design and Usage Data Warehouse Implementation https://homepages.cwi.nl/~manegold/DBDM/ http://liacs.leidenuniv.nl/~bakkerem2/dbdm/ Summary [email protected] [email protected] 3 Databases and Data Mining 2018 What is a Data Warehouse? Data Warehouse—Subject-Oriented Defined in many different ways, but not rigorously Organized around major subjects, such as customer, product, sales A decision support database that is maintained separately from the organization’s operational database Focusing on the modeling and analysis of data for decision makers, not on daily Support information processing by providing a solid platform of operations or transaction processing consolidated, historical data for analysis Provide a simple and concise view around particular subject issues by excluding “A data warehouse is a subject-oriented, integrated, time-variant, and data that are not useful in the decision support process nonvolatile collection of data in support of management’s decision-making process.”—W. H. Inmon Data warehousing: The process of constructing and using data warehouses 4 5 Data Warehouse—Integrated Data Warehouse—Time Variant Constructed by integrating multiple, heterogeneous data sources The time horizon for the data warehouse is significantly longer than that of relational databases, flat files, on-line transaction records operational systems Data cleaning and data integration techniques are applied. Operational database: current value data Ensure consistency in naming conventions, encoding structures, attribute Data warehouse data: provide information from a historical perspective (e.g., measures, etc. among different data sources past 5-10 years) Ex. Hotel price: differences on currency, tax, breakfast covered, and parking Every key structure in the data warehouse When data is moved to the warehouse, it is converted Contains an element of time, explicitly or implicitly But the key of operational data may or may not contain “time element” 6 7 Data Warehouse—Nonvolatile OLTP vs. OLAP OLTP OLAP Independence OLTP: Online transactional users clerk, IT professional knowledge worker A physically separate store of data transformed from the operational processing function day to day operations decision support DB design application-oriented subject-oriented environment DBMS operations data current, up-to-date historical, detailed, flat relational summarized, Static: Operational update of data does not occur in the data warehouse Query and transactional isolated multidimensional environment processing integrated, consolidated usage repetitive ad-hoc Does not require transaction processing, recovery, and concurrency control OLAP: Online analytical access read/write lots of scans index/hash on prim. key mechanisms processing unit of work short, simple complex query transaction Requires only two operations in data accessing: Data warehouse operations # records accessed tens millions initial loading of data and access of data Drilling, slicing, dicing, etc. #users thousands hundreds DB size 100MB-GB 100GB-TB metric transaction throughput query throughput, response 8 9 Why a Separate Data Warehouse? Data Warehouse: High performance for both systems A Multi-Tiered DBMS— tuned for OLTP: access methods, indexing, concurrency control, recovery Architecture Warehouse—tuned for OLAP: complex OLAP queries, multidimensional view, consolidation Top Tier: Front-End Tools Different functions and different data: missing data: Decision support requires historical data which operational DBs do Middle Tier: OLAP Server not typically maintain data consolidation: DS requires consolidation (aggregation, summarization) of Bottom Tier: Data data from heterogeneous sources Warehouse Server data quality: different sources typically use inconsistent data representations, codes and formats which have to be reconciled Data Note: There are more and more systems which perform OLAP analysis directly on 10 relational databases 11 Three Data Warehouse Models Extraction, Transformation, and Loading (ETL) Data extraction Enterprise warehouse get data from multiple, heterogeneous, and external sources Collects all of the information about subjects spanning the entire organization Data cleaning Data Mart detect errors in the data and rectify them when possible A subset of corporate-wide data that is of value to a specific groups of users Data transformation Its scope is confined to specific, selected groups, such as marketing data mart convert data from legacy or host format to warehouse format Independent vs. dependent (directly from warehouse) data mart Load Virtual warehouse sort, summarize, consolidate, compute views, check integrity, and build indicies A set of views over operational databases and partitions Only some of the possible summary views may be materialized Refresh propagate the updates from the data sources to the warehouse 12 13 Chapter 4: Data Warehousing and On-line Analytical From Tables and Spreadsheets to Data Cubes Processing A data warehouse is based on a multidimensional data model which views data in the form of a data cube Data Warehouse: Basic Concepts A data cube, such as sales, allows data to be modeled and viewed in multiple dimensions Data Warehouse Modeling: Data Cube and OLAP Dimension tables, such as item (item_name, brand, type), or time(day, week, month, quarter, year) Data Warehouse Design and Usage Fact table contains measures (such as dollars_sold) and keys to each of the related dimension tables Data Warehouse Implementation Data cube: A lattice of cuboids In data warehousing literature, an n-D base cube is called a base cuboid Summary The top most 0-D cuboid, which holds the highest-level of summarization, is called the apex cuboid The lattice of cuboids forms a data cube. 15 16 Data Cube: A Lattice of Cuboids Conceptual Modeling of Data Warehouses all Modeling data warehouses: dimensions & measures 0-D (apex) cuboid Star schema: A fact table in the middle connected to a set of dimension tables time item location supplier 1-D cuboids Snowflake schema: A refinement of star schema where some dimensional time,location item,location location,supplier hierarchy is normalized into a set of smaller dimension tables, forming a shape time,item 2-D cuboids time,supplier item,supplier similar to snowflake time,location,supplier 3-D cuboids Fact constellations: Multiple fact tables share dimension tables, viewed as a time,item,location time,item,supplier item,location,supplier collection of stars, therefore called galaxy schema or fact constellation 4-D (base) cuboid time, item, location, supplier 17 17 18 Star Schema: An Example Snowflake Schema: An Example time time time_key item time_key item day day item_key item_key Sales Fact Table supplier day_of_the_week Sales Fact Table item_name day_of_the_week item_name supplier_key month month brand brand time_key supplier_type quarter time_key type quarter type year year supplier_key item_key supplier_type item_key branch_key branch_key location location branch branch location_key location_key location_key branch_key location_key branch_key street branch_name units_sold street branch_name units_sold city_key branch_type city branch_type city dollars_sold state_or_province dollars_sold country city_key avg_sales avg_sales city state_or_province Measures Measures country 19 19 20 Fact Constellation: An Example A Concept Hierarchy for a Dimension (location) time time_key item Shipping Fact Table all all day item_key day_of_the_week Sales Fact Table item_name time_key month brand Europe ... North_America quarter time_key type item_key region year supplier_type shipper_key item_key from_location branch_key country Germany ... Spain Canada ... Mexico branch location_key location to_location branch_key units_sold location_key dollars_cost branch_name street city Frankfurt ... Vancouver ... Toronto branch_type dollars_sold city units_shipped province_or_state avg_sales country shipper L. Chan ... M. Wind Measures shipper_key office shipper_name location_key 21 shipper_type 22 Data Cube Measures: Three Categories Multidimensional Data Distributive: if the result derived by applying the function to n aggregate values is the same as that derived by applying the function on all the data without Sales volume as a function of product, month, and region partitioning Dimensions: Product, Location, Time Hierarchical summarization paths E.g., count(), sum(), min(), max() Algebraic: if it can be computed by an algebraic function with M arguments (where M is a bounded integer), each of which is obtained by applying a distributive Industry Region Year aggregate function Category Country Quarter avg(x) = sum(x) / count(x) Product City Month Week Is min_N() an algebraic measure? How about standard_deviation()? Product Office Day Holistic: if there is no constant bound on the storage size needed to describe a subaggregate. Month E.g., median(), mode(), rank() 23 25 A Sample Data Cube Cuboids Corresponding to the Cube Total annual sales Date of TVs in U.S.A. 1Qtr 2Qtr 3Qtr sum TV 4Qtr all PC U.S.A 0-D (apex) cuboid VCR product date country sum 1-D cuboids Canada product,date product,country date, country Mexico Country 2-D cuboids sum 3-D (base) cuboid product,
Recommended publications

  • Data Warehouse Fundamentals for Storage Professionals – What You Need to Know EMC Proven Professional Knowledge Sharing 2011

    Data Warehouse Fundamentals for Storage Professionals – What You Need To Know EMC Proven Professional Knowledge Sharing 2011 Bruce Yellin Advisory Technology Consultant EMC Corporation [email protected] Table of Contents Introduction ................................................................................................................................ 3 Data Warehouse Background .................................................................................................... 4 What Is a Data Warehouse? ................................................................................................... 4 Data Mart Defined .................................................................................................................. 8 Schemas and Data Models ..................................................................................................... 9 Data Warehouse Design – Top Down or Bottom Up? ............................................................10 Extract, Transformation and Loading (ETL) ...........................................................................11 Why You Build a Data Warehouse: Business Intelligence .....................................................13 Technology to the Rescue?.......................................................................................................19 RASP - Reliability, Availability, Scalability and Performance ..................................................20 Data Warehouse Backups .....................................................................................................26
  • Normalized Form Snowflake Schema

    Normalized Form Snowflake Schema

    Normalized Form Snowflake Schema Half-pound and unascertainable Wood never rhubarbs confoundedly when Filbert snore his sloop. Vertebrate or leewardtongue-in-cheek, after Hazel Lennie compartmentalized never shreddings transcendentally, any misreckonings! quite Crystalloiddiverted. Euclid grabbles no yorks adhered The star schemas in this does not have all revenue for this When done use When doing table contains less sensible of rows Snowflake Normalizationde-normalization Dimension tables are in normalized form the fact. Difference between Star Schema & Snow Flake Schema. The major difference between the snowflake and star schema models is slot the dimension tables of the snowflake model may want kept in normalized form to. Typically most of carbon fact tables in this star schema are in the third normal form while dimensional tables are de-normalized second normal. A relation is danger to pause in First Normal Form should each attribute increase the. The model is lazy in single third normal form 1141 Options to Normalize Assume that too are 500000 product dimension rows These products fall under 500. Hottest 'snowflake-schema' Answers Stack Overflow. Learn together is Star Schema Snowflake Schema And the Difference. For step three within the warehouses we tested Redshift Snowflake and Bigquery. On whose other hand snowflake schema is in normalized form. The CWM repository schema is a standalone product that other products can shareeach product owns only. The main difference between in two is normalization. Families of normalized form snowflake schema snowflake. Star and Snowflake Schema in Data line with Examples. Is spread the dimension tables in the snowflake schema are normalized. Like price weight speed and quantitiesie data execute a numerical format.
  • The Design of Multidimensional Data Model Using Principles of the Anchor Data Modeling: an Assessment of Experimental Approach Based on Query Execution Performance

    The Design of Multidimensional Data Model Using Principles of the Anchor Data Modeling: an Assessment of Experimental Approach Based on Query Execution Performance

    WSEAS TRANSACTIONS on COMPUTERS Radek Němec, František Zapletal The Design of Multidimensional Data Model Using Principles of the Anchor Data Modeling: An Assessment of Experimental Approach Based on Query Execution Performance RADEK NĚMEC, FRANTIŠEK ZAPLETAL Department of Systems Engineering Faculty of Economics, VŠB - Technical University of Ostrava Sokolská třída 33, 701 21 Ostrava CZECH REPUBLIC [email protected], [email protected] Abstract: - The decision making processes need to reflect changes in the business world in a multidimensional way. This includes also similar way of viewing the data for carrying out key decisions that ensure competitiveness of the business. In this paper we focus on the Business Intelligence system as a main toolset that helps in carrying out complex decisions and which requires multidimensional view of data for this purpose. We propose a novel experimental approach to the design a multidimensional data model that uses principles of the anchor modeling technique. The proposed approach is expected to bring several benefits like better query execution performance, better support for temporal querying and several others. We provide assessment of this approach mainly from the query execution performance perspective in this paper. The emphasis is placed on the assessment of this technique as a potential innovative approach for the field of the data warehousing with some implicit principles that could make the process of the design, implementation and maintenance of the data warehouse more effective. The query performance testing was performed in the row-oriented database environment using a sample of 10 star queries executed in the environment of 10 sample multidimensional data models.
  • Chapter 7 Multi Dimensional Data Modeling

    Chapter 7 Multi Dimensional Data Modeling

    Chapter 7 Multi Dimensional Data Modeling Fundamentals of Business Analytics” Content of this presentation has been taken from Book “Fundamentals of Business Analytics” RN Prasad and Seema Acharya Published by Wiley India Pvt. Ltd. and it will always be the copyright of the authors of the book and publisher only. Basis • You are already familiar with the concepts relating to basics of RDBMS, OLTP, and OLAP, role of ERP in the enterprise as well as “enterprise production environment” for IT deployment. In the previous lectures, you have been explained the concepts - Types of Digital Data, Introduction to OLTP and OLAP, Business Intelligence Basics, and Data Integration . With this background, now its time to move ahead to think about “how data is modelled”. • Just like a circuit diagram is to an electrical engineer, • an assembly diagram is to a mechanical Engineer, and • a blueprint of a building is to a civil engineer • So is the data models/data diagrams for a data architect. • But is “data modelling” only the responsibility of a data architect? The answer is Business Intelligence (BI) application developer today is involved in designing, developing, deploying, supporting, and optimizing storage in the form of data warehouse/data marts. • To be able to play his/her role efficiently, the BI application developer relies heavily on data models/data diagrams to understand the schema structure, the data, the relationships between data, etc. In this lecture, we will learn • About basics of data modelling • How to go about designing a data model at the conceptual and logical levels? • Pros and Cons of the popular modelling techniques such as ER modelling and dimensional modelling Case Study – “TenToTen Retail Stores” • A new range of cosmetic products has been introduced by a leading brand, which TenToTen wants to sell through its various outlets.
  • Master Data Management Whitepaper.Indd

    Master Data Management Whitepaper.Indd

    Creating a Master Data Environment An Incremental Roadmap for Public Sector Organizations Master Data Management (MDM) is the processes and technologies used to create and maintain consistent and accurate representations of master data. Movements toward modularity, service orientation, and SaaS make Master Data Management a critical issue. Master Data Management leverages both tools and processes that enable the linkage of critical data through a unifi ed platform that provides a common point of reference. When properly done, MDM streamlines data management and sharing across the enterprise among different areas to provide more effective service delivery. CMA possesses more than 15 years of experience in Master Data Management and more than 20 in data management and integration. CMA has also focused our efforts on public sector since our inception, more than 30 years ago. This document describes the fundamental keys to success for developing and maintaining a long term master data program within a public service organization. www.cma.com 2 Understanding Master Data transactional data. As it becomes more volatile, it typically is considered more transactional. Simple Master Data Behavior entities are rarely a challenge to manage and are rarely Master data can be described by the way that it interacts considered master-data elements. The less complex an with other data. For example, in transaction systems, element, the less likely the need to manage change for master data is almost always involved with transactional that element. The more valuable the data element is to data. This relationship between master data and the organization, the more likely it will be considered a transactional data may be fundamentally viewed as a master data element.
  • ER/Studio Enterprise Data Modeling

    ER/Studio Enterprise Data Modeling

    ER/Studio Enterprise Data Modeling ER/Studio®, a model-driven data architecture and database design solution, helps companies discover, document, and reuse data assets. With round-trip database support, data architects have the power to thoroughly analyze existing data sources as well as design and implement high quality databases that reflect business needs. The highly-readable visual format enhances communication across job functions, from business analysts to application developers. ER/Studio Enterprise also enables team and enterprise collaboration with its repository. • Enhance visibility into your existing data assets • Effectively communicate models across the enterprise Related Products • Improve data consistency • Trace data origins and whereabouts to enhance data integration and accuracy ER/Studio Viewer View, navigate and print ER/Studio ENHANCE VISIBILITY INTO YOUR EXISTING DATA ASSETS models in a view-only environ- ment. As data volumes grow and environments become more complex corporations find it increasingly difficult to leverage their information. ER/Studio provides an easy- Describe™ to-use visual medium to document, understand, and publish information about data assets so that they can be harnessed to support business objectives. Powerful Design, document, and maintain reverse engineering of industry-leading database systems allow a data modeler to enterprise applications written in compare and consolidate common data structures without creating unnecessary Java, C++, and IDL for better code duplication. Using industry standard notations, data modelers can create an infor- quality and shorter time to market. mation hub by importing, analyzing, and repurposing metadata from data sources DT/Studio® such as business intelligence applications, ETL environments, XML documents, An easy-to-use visual medium to and other modeling solutions.
  • Advantages of Dimensional Data Modeling

    Advantages of Dimensional Data Modeling

    Advantages of Dimensional Data Modeling 2997 Yarmouth Greenway Drive Madison, WI 53711 (608) 278-9964 www.sys-seminar.com Advantages of Dimensional Data Modeling 1 Top Ten Reasons Why Your Data Model Needs a Makeover 1. Ad hoc queries are difficult to construct for end-users or must go through database “gurus.” 2. Even standard reports require considerable effort and detail knowledge of the database. 3. Data is not integrated or is inconsistent across sources. 4. Changes in data values or in data sources cannot be handled gracefully. 5. The structure of the data does not mirror business processes or business rules. 6. The data model limits which BI tools can be used. 7. There is no system for maintaining change history or collecting metadata. 8. Disk space is wasted on redundant values. 9. Users who might benefit from the data don’t use it. 10.Maintenance is tedious and ad hoc. 2 Advantages of Dimensional Data Modeling Part 1 3 Part 1 - Data Model Overview •What is data modeling and why is it important? •Three common data models: de-normalized (SAS data sets) normalized dimensional model •Benefits of the dimensional model 4 What is data modeling? • The generalized logical relationship among tables • Usually reflected in the physical structure of the tables • Not tied to any particular product or DBMS • A critical design consideration 5 Why is data modeling important? •Allows you to optimize performance •Allows you to minimize costs •Facilitates system documentation and maintenance • The dimensional data model is the foundation of a well designed data mart or data warehouse 6 Common data models Three general data models we will review: De-normalized Expected by many SAS procedures Normalized Often used in transaction based systems such as order entry Dimensional Often used in data warehouse systems and systems subject to ad hoc queries.
  • Data Warehouse Applications in Modern Day Business

    Data Warehouse Applications in Modern Day Business

    California State University, San Bernardino CSUSB ScholarWorks Theses Digitization Project John M. Pfau Library 2002 Data warehouse applications in modern day business Carla Mounir Issa Follow this and additional works at: https://scholarworks.lib.csusb.edu/etd-project Part of the Business Intelligence Commons, and the Databases and Information Systems Commons Recommended Citation Issa, Carla Mounir, "Data warehouse applications in modern day business" (2002). Theses Digitization Project. 2148. https://scholarworks.lib.csusb.edu/etd-project/2148 This Project is brought to you for free and open access by the John M. Pfau Library at CSUSB ScholarWorks. It has been accepted for inclusion in Theses Digitization Project by an authorized administrator of CSUSB ScholarWorks. For more information, please contact [email protected]. DATA WAREHOUSE APPLICATIONS IN MODERN DAY BUSINESS A Project Presented to the Faculty of California State University, San Bernardino In Partial Fulfillment of the Requirements for the Degree Master of Business Administration by Carla Mounir Issa June 2002 DATA WAREHOUSE APPLICATIONS IN MODERN DAY BUSINESS A Project Presented to the Faculty of California State University, San Bernardino by Carla Mounir Issa June 2002 Approved by: Date Dr. Walter T. Stewart ABSTRACT Data warehousing is not a new concept in the business world. However, the constant changing application of data warehousing is what is being innovated constantly. It is these applications that are enabling managers to make better decisions through strategic planning, and allowing organizations to achieve a competitive advantage. The technology of implementing the data warehouse will help with the decision making process, analysis design, and will be more cost effective in the future.
  • Lecture Notes on Data Mining& Data Warehousing

    Lecture Notes on Data Mining& Data Warehousing

    LECTURE NOTES ON DATA MINING& DATA WAREHOUSING COURSE CODE:BCS-403 DEPT OF CSE & IT VSSUT, Burla SYLLABUS: Module – I Data Mining overview, Data Warehouse and OLAP Technology,Data Warehouse Architecture, Stepsfor the Design and Construction of Data Warehouses, A Three-Tier Data WarehouseArchitecture,OLAP,OLAP queries, metadata repository,Data Preprocessing – Data Integration and Transformation, Data Reduction,Data Mining Primitives:What Defines a Data Mining Task? Task-Relevant Data, The Kind of Knowledge to be Mined,KDD Module – II Mining Association Rules in Large Databases, Association Rule Mining, Market BasketAnalysis: Mining A Road Map, The Apriori Algorithm: Finding Frequent Itemsets Using Candidate Generation,Generating Association Rules from Frequent Itemsets, Improving the Efficiently of Apriori,Mining Frequent Itemsets without Candidate Generation, Multilevel Association Rules, Approaches toMining Multilevel Association Rules, Mining Multidimensional Association Rules for Relational Database and Data Warehouses,Multidimensional Association Rules, Mining Quantitative Association Rules, MiningDistance-Based Association Rules, From Association Mining to Correlation Analysis Module – III What is Classification? What Is Prediction? Issues RegardingClassification and Prediction, Classification by Decision Tree Induction, Bayesian Classification, Bayes Theorem, Naïve Bayesian Classification, Classification by Backpropagation, A Multilayer Feed-Forward Neural Network, Defining aNetwork Topology, Classification Based of Concepts from
  • Bio-Ontologies Submission Template

    Bio-Ontologies Submission Template

    Relational to RDF mapping using D2R for translational research in neuroscience Rudi Verbeeck*1, Tim Schultz2, Laurent Alquier3 and Susie Stephens4 Johnson & Johnson Pharmaceutical Research and Development 1 Turnhoutseweg 30, Beerse, Belgium; 2 Welch & McKean Roads, Spring House, PA, United States; 3 1000 Route 202, Rari- tan, NJ, United States and 4 145 King of Prussia Road, Radnor, PA, United States ABSTRACT Relational database technology has been developed as an Motivation: To support translational research and external approach for managing and integrating data in a highly innovation, we are evaluating the potential of the semantic available, secure and scalable architecture. With this ap- web to integrate data from discovery research through to the proach, all metadata is embedded or implicit in the applica- clinical environment. This paper describes our experiences tion or metadata schema itself, which results in performant in mapping relational databases to RDF for data sets relating queries. However, this architecture makes it difficult to to neuroscience. share data across a large organization where different data- Implementation: We describe how classes were identified base schemata and applications are being used. in the original data sets and mapped to RDF, and how con- Semantic web offers a promising approach to interconnect nections were made to public ontologies. Special attention databases across an organization, since the technology was was paid to the mapping of experimental measures to RDF designed to function within the distributed environment of and how it was impacted by the relational schemata. the web. Resource Description Framework (RDF) and Web Results: Mapping from relational databases to RDF can Ontology Language (OWL) are the two main semantic web benefit from techniques borrowed from dimensional model- standard recommendations.
  • Database Vs. Data Warehouse: a Comparative Review

    Database Vs. Data Warehouse: a Comparative Review

    Insights Database vs. Data Warehouse: A Comparative Review By Drew Cardon Professional Services, SVP Health Catalyst A question I often hear out in the field is: I already have a database, so why do I need a data warehouse for healthcare analytics? What is the difference between a database vs. a data warehouse? These questions are fair ones. For years, I’ve worked with databases in healthcare and in other industries, so I’m very familiar with the technical ins and outs of this topic. In this post, I’ll do my best to introduce these technical concepts in a way that everyone can understand. But, before we discuss the difference, could I ask one big favor? This will only take 10 seconds. Could you click below and take a quick poll? I’d like to find out if your organization has a data warehouse, data base(s), or if you don’t know? This would really help me better understand how prevalent data warehouses really are. Click to take our 10 second database vs data warehouse poll Before diving in to the topic, I want to quickly highlight the importance of analytics in healthcare. If you don’t understand the importance of analytics, discussing the distinction between a database and a data warehouse won’t be relevant to you. Here it is in a nutshell. The future of healthcare depends on our ability to use the massive amounts of data now available to drive better quality at a lower cost. If you can’t perform analytics to make sense of your data, you’ll have trouble improving quality and costs, and you won’t succeed in the new healthcare environment.
  • MASTER's THESIS Role of Metadata in the Datawarehousing Environment

    MASTER's THESIS Role of Metadata in the Datawarehousing Environment

    2006:24 MASTER'S THESIS Role of Metadata in the Datawarehousing Environment Kranthi Kumar Parankusham Ravinder Reddy Madupu Luleå University of Technology Master Thesis, Continuation Courses Computer and Systems Science Department of Business Administration and Social Sciences Division of Information Systems Sciences 2006:24 - ISSN: 1653-0187 - ISRN: LTU-PB-EX--06/24--SE Preface This study is performed as the part of the master’s programme in computer and system sciences during 2005-06. It has been very useful and valuable experience and we have learned a lot during the study, not only about the topic at hand but also to manage to the work in the specified time. However, this workload would not have been manageable if we had not received help and support from a number of people who we would like to mention. First of all, we would like to thank our professor Svante Edzen for his help and supervision during the writing of thesis. And also we would like to express our gratitude to all the employees who allocated their valuable time to share their professional experience. On a personal level, Kranthi would like to thank all his family for their help and especially for my friends Kiran, Chenna Reddy, and Deepak Kumar. Ravi would like to give the greatest of thanks to his family for always being there when needed, and constantly taking so extremely good care of me….Also, thanks to all my friends for being close to me. Luleå University of Technology, 31 January 2006 Kranthi Kumar Parankusham Ravinder Reddy Madupu Abstract In order for a well functioning data warehouse to succeed many components must work together.