B.

Tech CE2 6th Semester

J. C Bose University of
Science & Technology,
YMCA, Faridabad
 Data Warehousing and OLAP Technology

 What is a data warehouse?

 A multi-dimensional data model

 Data warehouse architecture

 Data warehouse implementation

 From data warehousing to data mining

2
 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 a subject-oriented, integrated, time-variant, and 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
3
 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

4
 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.

5
 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”
6
 Data Warehouse—Nonvolatile
 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

7
 Data Warehouse: Update-Driven Approach

8
 Data Warehouse vs. Heterogeneous DBMS
 Traditional heterogeneous DB integration: A query driven approach

 Build wrappers/mediators on top of heterogeneous databases

 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
OLTP OLAP
users clerk, IT professional knowledge worker
function day to day operations decision support
DB design application-oriented subject-oriented
data current, up-to-date historical,
detailed, flat relational summarized, multidimensional
isolated integrated, consolidated
usage repetitive ad-hoc
access read/write lots of scans
index/hash on prim. key
unit of work short, simple transaction complex query
# records accessed tens millions
#users thousands hundreds
DB size 100MB-GB 100GB-TB
metric transaction throughput query throughput, response

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
 Note: There are more and more systems which perform OLAP analysis directly on
12 relational databases
 Data Warehouse Multi-tiered Architecture
 Bottom tier: It is a warehouse database server that is almost always a
relational database system. Back-end tools and utilities are used to feed data
into the bottom tier from operational databases or other external sources.

 Middle tier: It is OLAP server that is typically implemented using either:

 Relational OLAP (ROLAP) model (i.e., an extended relational DBMS that
maps operations on multidimensional data to standard relational
operations); or
 Multidimensional OLAP (MOLAP) model (i.e., a special-purpose server
that directly implements multidimensional data and operations).
 Hybrid OLAP (HOLAP) model (i.e. combining the functionalities of both
ROLAP & MOLAP)

13
 Top tier: it is a front-end client layer, which contains query and reporting
 Data
Warehouse
3-Tier
Architecture

14
Data Warehouse: A Multi-Tiered Architecture

Monitor
& OLAP Server
Other Metadata
sources Integrator

Analysis
Operational Extract Query
DBs Transform Data Serve Reports
Load
Refresh
Warehouse Data mining

Data Marts

Data Sources Data Storage OLAP Engine Front-End Tools

 Data Warehouse Back-End Tools and Utilities
 Data extraction
 get data from multiple, heterogeneous, and external sources
 Data cleaning
 detect errors in the data and rectify them when possible
 Data transformation and integration
 convert data from legacy or host format to warehouse format
 Load
 sort, summarize, consolidate, compute views, check integrity, and build
indicies and partitions
 Refresh
 propagate the updates from the data sources to the warehouse

16
 Data Warehouse Models: Enterprise Warehouse,
Data Mart, and Virtual Warehouse
Enterprise warehouse: An enterprise warehouse collects all of the information about subjects spanning
the entire organization.
 It provides corporate-wide data integration, usually from one or more operational systems or
external information providers, and is cross-functional in scope.
 It typically contains detailed data as well as summarized data, and can range in size from a few
gigabytes to hundreds of gigabytes, terabytes, or beyond.
 An enterprise data warehouse may be implemented on traditional mainframes, computer
super-servers, or parallel architecture platforms.
 It requires extensive business modeling and may take years to design and build.
Data mart: A data mart contains a subset of corporate-wide data that is of value to a specific group of
users.
 The scope is confined to specific selected subjects. For example, a marketing data mart may
confine its subjects to customer, item, and sales.
 The data contained in data marts tend to be summarized.
 Data marts are usually implemented on low-cost departmental servers that are Unix/Linux or
Windows based.
17  The implementation cycle of a data mart is more likely to be measured in weeks rather than
 Types of Data Marts
Depending on the source of data, data marts can be categorized as
independent or dependent.
 Independent data marts are sourced from data captured from one
or more operational systems or external information providers, or
from data generated locally within a particular department or
geographic area.
 Dependent data marts are sourced directly from enterprise data
warehouses.

18
 Virtual Data Warehouse
 A virtual warehouse is a set of views over operational
databases.
 For efficient query processing, only some of the possible
summary views may be materialized. A virtual warehouse is
easy to build but requires excess capacity on operational
database servers.

19
 Design of Data Warehouse: A Business Analysis Framework

 Four views regarding the design of a data warehouse

 Top-down view
 allows selection of the relevant information necessary for the data warehouse
 Data source view
 exposes the information being captured, stored, and managed by operational
systems
 Data warehouse view
 consists of fact tables and dimension tables
 Business query view
 sees the perspectives of data in the warehouse from the view of end-user
20
 Data Warehouse Design Process
 Top-down, bottom-up approaches or a combination of both
 Top-down: Starts with overall design and planning (mature)
 Bottom-up: Starts with experiments and prototypes (rapid)
 From software engineering point of view
 Waterfall: structured and systematic analysis at each step before proceeding to the next
 Spiral: rapid generation of increasingly functional systems, short turn around time, quick turn
around
 Typical data warehouse design process
 Choose a business process to model, e.g., orders, invoices, etc.
 Choose the grain (atomic level of data) of the business process
 Choose the dimensions that will apply to each fact table record
 Choose the measure that will populate each fact table record

21
 Recommended
Approach
 A recommended method for
the development of data
warehouse systems is to
implement the warehouse in
an incremental and
evolutionary manner,

22
 Metadata Repository
Meta data is the data defining warehouse objects. It stores:
 Description of the structure of the data warehouse
 schema, view, dimensions, hierarchies, derived data defn, data mart locations and contents
 Operational meta-data
 data lineage (history of migrated data and transformation path), currency of data (active,
archived, or purged), monitoring information (warehouse usage statistics, error reports, audit
trails)
 The algorithms used for summarization
 The mapping from operational environment to the data warehouse
 Data related to system performance
 Business data
 business terms and definitions, ownership of data, charging policies

23
 OLAP Server Architectures
 Relational OLAP (ROLAP)
 Use relational or extended-relational DBMS to store and manage warehouse data and OLAP
middle ware
 Include optimization of DBMS backend, implementation of aggregation navigation logic, and
additional tools and services
 Greater scalability
 Multidimensional OLAP (MOLAP)
 Sparse array-based multidimensional storage engine
 Fast indexing to pre-computed summarized data
 Hybrid OLAP (HOLAP) (e.g., Microsoft SQLServer)
 Flexibility, e.g., low level: relational, high-level: array
 Specialized SQL servers (e.g., Redbricks)
 Specialized support for SQL queries over star/snowflake schemas

24
 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
25
 Example of Star Schema
time
time_key item
day item_key
day_of_the_week Sales Fact Table item_name
month brand
quarter time_key type
year supplier_type
item_key
branch_key
branch location
location_key
branch_key location_key
branch_name units_sold street
branch_type city
dollars_sold state_or_province
country
avg_sales
Measures

26
 Example of Snowflake Schema
time
time_key item
day item_key supplier
day_of_the_week Sales Fact Table item_name supplier_key
month brand supplier_type
quarter time_key type
year item_key supplier_key

branch_key
location
branch location_key
location_key
branch_key
units_sold street
branch_name
city_key
branch_type
dollars_sold city
city_key
avg_sales city
state_or_province
Measures country

27
 Example of Fact Constellation
time
time_key item Shipping Fact Table
day item_key
day_of_the_week Sales Fact Table item_name time_key
month brand
quarter time_key type item_key
year supplier_type shipper_key
item_key
branch_key from_location

branch location_key location to_location

branch_key location_key dollars_cost
branch_name
units_sold
street
branch_type dollars_sold city units_shipped
province_or_state
avg_sales country shipper
Measures shipper_key
shipper_name
location_key
28 shipper_type
 A Concept Hierarchy: Dimension (location)

all all

region Europe ... North_America

country Germany ... Spain Canada ... Mexico

city Frankfurt ... Vancouver ... Toronto

office L. Chan ... M. Wind

29
 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
 Dimension tables, such as item (item_name, brand, type), or time(day, week, month,
quarter, year)
 Fact table contains measures (such as dollars_sold) and keys to each of the related
dimension tables
 In data warehousing literature, an n-D base cube is called a base cuboid. 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.
30
 Multidimensional Data

 Sales volume as a function of product, month, and

region
Dimensions: Product, Location, Time
Hierarchical summarization paths

Industry Region Year

Category Country Quarter

Product

Product City Month Week

Office Day

Month
31
 A Sample Data Cube
Total annual sales
Date of TV in U.S.A.
1Qtr 2Qtr 3Qtr 4Qtr sum
TV
PC U.S.A
VCR

Country
sum
Canada

Mexico

sum

32
 Cuboids Corresponding to the Cube

all
0-D(apex) cuboid
product date country
1-D cuboids

product,date product,country date, country

2-D cuboids

3-D(base) cuboid
product, date, country

33
 Cube: A Lattice of Cuboids
all
0-D(apex) cuboid

time item location

supplier 1-D cuboids

location,supplier
time,item time,location item,location
2-D cuboids
time,supplier item,supplier

time,location,supplier 3-D cuboids

item,location,supplier
time,item,location time,item,supplier

4-D(base) cuboid
time, item, location, supplier
34
 Typical OLAP Operations
 Roll up (drill-up): summarize data
 by climbing up hierarchy or by dimension reduction
 Drill down (roll down): reverse of roll-up
 from higher level summary to lower level summary or detailed data, or introducing
new dimensions
 Slice and dice: project and select
 Pivot (rotate):
 reorient the cube, visualization, 3D to series of 2D planes
 Other 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)
35
 Roll-Up Operation
 Also called the drill-up operation.
 Performs aggregation on a data cube, either by
climbing up a concept hierarchy for a
dimension or by dimension reduction.
 Fig shows the result of a roll-up operation
performed on the central cube by climbing up
the concept hierarchy for location.
 This hierarchy was defined as the total order
“street < city < province or state < country.” The
roll-up operation shown aggregates the data by
ascending the location hierarchy from the level
of city to the level of country.
 Example: roll-up on location (from cities to
countries)
 When roll-up is performed by dimension
reduction, one or more dimensions are
removed from the given cube.

36
 Drill-Down
 Drill-down is the reverse of roll-up.
 It navigates from less detailed data to
more detailed data.
 Drill-down can be realized by either
stepping down a concept hierarchy
for a dimension or introducing
additional dimensions.
 Example: drill-down on time (from
quarters to months)
 Because a drill-down adds more
detail to the given data, it can also be
performed by adding new dimensions
to a cube.
37
 Dice operation
 The dice operation defines a subcube by
performing a selection on two or more
dimensions.

 Example: Dice for (location =

“Toronto” or “Vancouver”) and (time
= “Q1” or “Q2”) and (item = “home
entertainment” or “computer”).

38
 Slice and Pivot
 The slice operation performs
a selection on one dimension
of the given cube, resulting in
a subcube.
 Example: slice for (time =
“Q1”)

 Pivot (also called rotate) is a

visualization operation that
rotates the data axes in view
to provide an alternative data
presentation.

39
 Efficient Data Cube Computation
 Data cube can be viewed as a lattice of cuboids
 The bottom-most cuboid is the base cuboid
 The top-most cuboid (apex) contains only one cell
 How many cuboids in an n-dimensional cube with L levels?
n
T   ( Li 1)
i 1
 Curse of Dimensionality: The storage requirements are even more excessive
when many of the dimensions have associated concept hierarchies, each
with multiple levels.
 Materialization of data cube
 Materialize every (cuboid) (full materialization), none (no materialization), or
some (partial materialization)
 Selection of which cuboids to materialize
40  Based on size, sharing, access frequency, etc.
 Cube Operation
 Cube definition and computation in DMQL
define cube sales[item, city, year]: sum (sales_in_dollars)
compute cube sales

 Transform it into a SQL-like language (with a new operator cube by, introduced by Gray et al.’96)
SELECT item, city, year, SUM (amount) ()
FROM SALES
CUBE BY item, city, year (city) (item) (year)

 Need not to compute multiple Group-Bys

(city, item) (city, year) (item, year)
(item, city, year),
(item, city), (item, year), (city, year),
(item), (city), (year) (city, item, year)
41 ()
 Indexing OLAP Data: Bitmap Index
 Index on a particular column
 Each value in the column has a bit vector: bit-op is fast
 The length of the bit vector: # of records in the base table
 The i-th bit is set if the i-th row of the base table has the value for the
indexed column
 not suitable for high cardinality domains

Base table Index on Region Index on Type

Cust Region Type RecIDAsia Europe America RecID Retail Dealer
C1 Asia Retail 1 1 0 0 1 1 0
C2 Europe Dealer 2 0 1 0 2 0 1
C3 Asia Dealer 3 1 0 0 3 0 1
C4 America Retail 4 0 0 1 4 1 0
C5 Europe Dealer 5 0 1 0 5 0 1
42
 Example: Bitmap indexing

43
 Indexing OLAP Data: Join Indices
 Join index: JI(R-id, S-id) where R (R-id, …)  S (S-id, …)
 Traditional indices map the values to a list of record ids
 It materializes relational join in JI file and speeds up
relational join
 In data warehouses, join index relates the values of the
dimensions of a start schema to rows in the fact table.
 E.g. fact table: Sales and two dimensions city and
product
 A join index on city maintains for each distinct city a
list of R-IDs of the tuples recording the Sales in the
city
 Join indices can span multiple dimensions

44
 Join Indexing: Example

Linkages between a sales fact table and

location and item dimension tables.

Join index tables based on the linkages between the sales

45 fact table and the location and item dimension tables
 Efficient Processing OLAP Queries
 Determine which operations should be performed on the available cuboids
 Transform drill, roll, etc. into corresponding SQL and/or OLAP operations, e.g., dice = selection +
projection
 Determine which materialized cuboid(s) should be selected for OLAP op.
 Let the query to be processed be on {brand, province_or_state} with the condition “year = 2004”, and
there are 4 materialized cuboids available:
1) {year, item_name, city}
2) {year, brand, country}
3) {year, brand, province_or_state}
4) {item_name, province_or_state} where year = 2004
Which should be selected to process the query?

46  Explore indexing structures and compressed vs. dense array structs in MOLAP
 Data Warehouse Usage
Three kinds of data warehouse applications
 Information processing
 supports querying, basic statistical analysis, and reporting using crosstabs, tables,
charts and graphs
 Analytical processing
 multidimensional analysis of data warehouse data
 supports basic OLAP operations, slice-dice, drilling, pivoting
 Data mining
 knowledge discovery from hidden patterns
 supports associations, constructing analytical models, performing classification and
prediction, and presenting the mining results using visualization tools
47
 Book Exercise

48
Thank You