Data Warehousing : and OLAP — BIS 541 — — Chapter 3 —

1. Data Warehousing: and OLAP—BIS 541— — Chapter 3 — 2013/2014 Summer

2. Chapter 3: Data Warehousing and OLAP Technology for Data Mining • What is a data warehouse? • A multi-dimensional data model • Data warehouse architecture • Data warehouse implementation • Further development of data cube technology • From data warehousing to data mining

3. What is Data Warehouse? • Defined in many different ways, but not rigorously. • A decision support database that is maintained separately from the organization’s operational database • Support information processing by providing a solid platform of consolidated, historical data for analysis. • “A data warehouse is asubject-oriented, integrated, time-variant, and nonvolatilecollection of data in support of management’s decision-making process.”—W. H. Inmon • Data warehousing: • The process of constructing and using data warehouses

4. Data Warehouse—Subject-Oriented • Organized around major subjects, such as customer, product, sales. • Focusing on the modeling and analysis of data for decision makers, not on daily operations or transaction processing. • Provide a simple and concise view around particular subject issues by excluding data that are not useful in the decision support process.

5. Data Warehouse—Integrated • Constructed by integrating multiple, heterogeneous data sources • relational databases, flat files, on-line transaction records • Data cleaning and data integration techniques are applied. • Ensure consistency in naming conventions, encoding structures, attribute measures, etc. among different data sources • E.g., Hotel price: currency, tax, breakfast covered, etc. • When data is moved to the warehouse, it is converted.

6. Data Warehouse—Time Variant • The time horizon for the data warehouse is significantly longer than that of operational systems. • Operational database: current value data. • Data warehouse data: provide information from a historical perspective (e.g., past 5-10 years) • Every key structure in the data warehouse • Contains an element of time, explicitly or implicitly • But the key of operational data may or may not contain “time element”.

7. Data Warehouse—Non-Volatile • A physically separate store of data transformed from the operational environment. • Operational update of data does not occur in the data warehouse environment. • Does not require transaction processing, recovery, and concurrency control mechanisms • Requires only two operations in data accessing: • initial loading of data and access of data.

8. Data Warehouse vs. Heterogeneous DBMS • Traditional heterogeneous DB integration: • Build wrappers/mediators on top of heterogeneous databases • Query driven approach • When a query is posed to a client site, a meta-dictionary is used to translate the query into queries appropriate for individual heterogeneous sites involved, and the results are integrated into a global answer set • Complex information filtering, compete for resources • Data warehouse: update-driven, high performance • Information from heterogeneous sources is integrated in advance and stored in warehouses for direct query and analysis

9. Data Warehouse vs. Operational DBMS • OLTP (on-line transaction processing) • Major task of traditional relational DBMS • Day-to-day operations: purchasing, inventory, banking, manufacturing, payroll, registration, accounting, etc. • OLAP (on-line analytical processing) • Major task of data warehouse system • Data analysis and decision making • Distinct features (OLTP vs. OLAP): • User and system orientation: customer vs. market • Data contents: current, detailed vs. historical, consolidated • Database design: ER + application vs. star + subject • View: current, local vs. evolutionary, integrated • Access patterns: update vs. read-only but complex queries

10. OLTP vs. OLAP

11. Why Separate Data Warehouse? • High performance for both systems • DBMS— tuned for OLTP: access methods, indexing, concurrency control, recovery • Warehouse—tuned for OLAP: complex OLAP queries, multidimensional view, consolidation. • Different functions and different data: • missing data: Decision support requires historical data which operational DBs do not typically maintain • data consolidation: DS requires consolidation (aggregation, summarization) of data from heterogeneous sources • data quality: different sources typically use inconsistent data representations, codes and formats which have to be reconciled

12. Chapter 2: Data Warehousing and OLAP Technology for Data Mining • What is a data warehouse? • A multi-dimensional data model • Data warehouse architecture • Data warehouse implementation • Further development of data cube technology • From data warehousing to data mining

13. From Tables and Spreadsheets to Data Cubes • A data warehouse is based on a multidimensional data model which views data in the form of a data cube • A data cube, such as sales, allows data to be modeled and viewed in multiple dimensions • Dimensions • A sale data warehouse with respect to dimension • time, item, branch, location • Dimension tables, such as • item (item_name, brand, type), or • time(day, week, month, quarter, year) • Facts: numerical measures • dollars_sold: sales amount in dollars • units_sold: number of units sold • Fact table contains measures (such as dollars_sold) and keys to each of the related dimension tables

14. A 2-D data cube: A table or spreadsheet for sales from AllElectronics AllElectronics sales data for items sold per quarter in the city of Istanbul Time dimension organized in quarters item dimension by types of items sold The fact or measure is dollar_sold

15. A three dimensional cube Dimensions: time, item, location for the cities

16. A Data Cube Representation of the same data • Sales volume as a function of product, month, and region Dimensions: Product, Location, Time Hierarchical summarization paths izmir locations ankara istabbul items phon comp Quarters Q1

17. A 4-D Cube as a series of 3-D cubes Dimensions: item,time,location,supplier From Supplier A From Supplier B From Supplier C locations items Quarters

18. n-Dimensional Cube • Any n-D data as a series of (n-1)-D “cubes” • In data warehousing literature, • A data cube is referred to as a cuboid • The lattice of cuboids forms a data cube. • The cuboid holding the lowest level of summarization is called a base cuboid. • the 4-D cuboid is the base cuboid for the given four dimensions • The top most 0-D cuboid, which holds the highest-level of summarization, is called the apex cuboid. • Here this is the total sales, or dollars_sold summarized over all four dimensions • typically denoted by all

19. Cube: A Lattice of Cuboids all 0-D(apex) cuboid time item location supplier 1-D cuboids time,item time,location item,location location,supplier 2-D cuboids time,supplier item,supplier time,location,supplier time,item,location 3-D cuboids item,location,supplier time,item,supplier 4-D(base) cuboid time, item, location, supplier

20. Conceptual Modeling of Data Warehouses • Modeling data warehouses: dimensions & measures • Star schema: A fact table in the middle connected to a set of dimension tables • Snowflake schema: A refinement of star schema where some dimensional hierarchy is normalized into a set of smaller dimension tables, forming a shape similar to snowflake • Fact constellations: Multiple fact tables share dimension tables, viewed as a collection of stars, therefore called galaxy schema or fact constellation

21. item time item_key item_name brand type supplier_type time_key day day_of_the_week month quarter year location branch location_key street city province_or_street country branch_key branch_name branch_type Example of Star Schema Sales Fact Table time_key item_key branch_key location_key units_sold dollars_sold avg_sales Measures

23. supplier item time item_key item_name brand type supplier_key supplier_key supplier_type time_key day day_of_the_week month quarter year city location branch city_key city province_or_street country location_key street city_key branch_key branch_name branch_type Example of Snowflake Schema Sales Fact Table time_key item_key branch_key location_key units_sold dollars_sold avg_sales Measures

24. A unnormalizedCity Table City province and Country is repeated For every steet in İstanbul A NormalizedCityTable Unnecessary repitations of province end country are eliminated Memory gain but complex queries

25. item time item_key item_name brand type supplier_type time_key day day_of_the_week month quarter year location location_key street city province_or_street country shipper branch shipper_key shipper_name location_key shipper_type branch_key branch_name branch_type Example of Fact Constellation Shipping Fact Table time_key Sales Fact Table item_key time_key shipper_key item_key from_location branch_key to_location location_key dollars_cost units_sold units_shipped dollars_sold avg_sales Measures

26. Example • The relational database scheme for AE: • time(time_key,day,day_of_week,month,quarter,year) • item(item_key,item_name,brand,type,supplier_type) • branch(branch_key,branch_name,branch_type) • location(location_key,street,city,province_or_state,country) • sales(time_key,item_key,branch_key,location_key,number_of_units_sold,price)

27. Example cont. • Select s.time_key,s.item_key,s.branch_key,s.location_key, • sum(s.number_of_units_sold*s.price), • sum(s.number_of_units_sold) • from time t, item i,branch b,location l,sales s, • where s.time_key=t.time_key and • s.item_key=i.item_key and • s.branch_key=b.branch_key and • s.location_key=l.location_key • group by s.time_key, s.item_key, s.branch_key,s.location_key

28. Example Cont. • The cube created is the base cuboid of the sales_star datacube • it contains all of the dimensions • granularity of each is at the join key level • by changing the group by clauses • E.g., • group by t.month: sum up the measures of each group by month • removing group by s.branch_key: generate a higher-level cuboid • recoving all group bys: total sum of dollars sold and total count of units_sold • zero-dimensional cuboid is apex cuboid

29. Time by month • Select t.year,t.month,s.item_key,s.branch_key,s.location_key,sum(s.number_of_units_sold*s.price),sum(s.number_of_units_sold) • from time t, item i,branch b,location l,sales s, • where s.time_key=t.time_key and • s.item_key=i.item_key and • s.branch_key=b.branch_key and • s.location_key=l.location_key • group by t.year, t.month, s.item_key, s.branch_key,s.location_key

30. A three dimensional cuboid • Select s.time_key,s.item_key, s.location_key, • sum(s.number_of_units_sold*s.price), • sum(s.number_of_units_sold) • from time t, item i,branch b,location l,sales s, • where s.time_key=t.time_key and • s.item_key=i.item_key and • s.branch_key=b.branch_key and • s.location_key=l.location_key • group by s.time_key, s.item_key,s.location_key

31. Concept hierarchies • Defines a sequence of mappings from a set of low-level concepts to high-level more general concepts • E.g., dimension location is described by • number,street,city,province_or_state,zipcode and country • are related by a total order, forming a concept hierarchy • street<city<province_or_state<country • The attributes of a dimension may be organized in a partial order, forming a lattice • day,week,month,quarter, year • day<[month<quarter,week]<year

32. A Concept Hierarchy: Dimension (location) all all Europe ... North_America region Germany ... Spain Canada ... Mexico country Vancouver ... city Frankfurt ... Toronto L. Chan ... M. Wind office

33. Partially ordered co • The attributes of a dimension may be organized in a partial order, forming a lattice • day,week,month,quarter, year • day<[month<quarter,week]<year • predefined in the data mining system • time • fiscal year starting on April 1 • academic year starting on September 1

34. Multidimensional Data • Sales volume as a function of product, month, and region Dimensions: Product, Location, Time Hierarchical summarization paths Region Industry Region Year Category Country Quarter Product City Month Week Office Day Product A partially ordered hierarchy Month

35. Cuboids Corresponding to the Cube all 0-D(apex) cuboid location item time 1-D cuboids item,time item,location time, location 2-D cuboids 3-D(base) cuboid item, time, location

36. Set grouping hierarchy • Set-grouping hierarchy: • discretizing or grouping values for a given dimension or attribute • Ex: price • There may be more than one concept hierarchy for a given attribute or dimension based on different user viewpoints • price by defining ranges for • inexpensive, moderately_priced,expensive

37. How defined? • provided by manually by • system users • domain experts • knowledge engineers or • automatically generated based on statistical analysis of the data distribution

38. Typical OLAP Operations • In the multidimensional model data are organized into multiple dimensions • each dimension contains multiple levels of abstraction defined by concept hierarchies • This organization provides users with the flexibility to view data from different perspectives

39. Example • Refer to figure 2.10 in Han’s book • data cube for AllElls sales • dimensions: location,time,item • location -- city • time -- quarters • item -- item types • measure displayed is dollars-sold

40. Cuboids Corresponding to the Cube all 0-D(apex) cuboid location item time 1-D cuboids item,time item,location time, location 2-D cuboids 3-D(base) cuboid item, time, location

41. Roll-up (drill-up) • Climbing up a concept hierarchy for a dimension or • by dimension reduction • Ex:roll-up operation aggregates data by ascending the location hierarchy • from the level of city • to the level of country • rather than grouping the data by city,the cubes • groups the data by country

42. By a drill up opperation examine sales By country rather than city level roll up

43. when performed by dimension reduction • one or more dimensions are removed from the cube • Ex a sales cube with location and time • roll-up may remove the time dimension • aggregation of total sales by location • rather than by location and by time Two dimensional cuboid One dim. cuboid

44. Drill-down (roll-down) • reverse of roll-up • navigates from less detailed data to more detailed data • from higher level summary to lower level summary or detailed data, or • stepping down a concept hierarchy for a dimension • introducing new dimensions • Ex: drill-down for time • day<month<quarter<year • form the level of quarter • to the more detailed level of month • Adding a new dimension to the data

45. Drill down

46. Slice and dice • Slice: a selection on one dimension of the cube • resulting in subcube • Ex: sale data are selected for dimension time using time =Q1 • dice: defines a subcube by performing a selection on two or more dimensions • Ex: a dice opp. Based on • location=“toronto” or “vencover” and • time =Q1 or Q2 and • item = “home entertainment” or “computer”

47. slice dice

48. Pivot (rotate) • Visualization opp. Rotates the data axes in view to provide an alternative presentation of data • Ex:item and location axes in a 2-D slice are rotated • or transforming a 3-D cube into a series of 2-D planes

49. Other OLAP operations • drill across: involving (across) more than one fact table • drill through: through the bottom level of the cube to its back-end relational tables (using SQL) • ranking the top N or bottom N items in lists • moving averages • growth rates • interests

50. Parent Child Dimensions • Based on two dimension table columns that together define the lieage relationships among the members of the dimension • Member key column:identifies each member • Parent key column: identifies the parent of each member