2. 2
Chapter 4: Data Warehousing and On-line
Analytical Processing
ā¼ Data Warehouse: Basic Concepts
ā¼ Data Warehouse Modeling: Data Cube and OLAP
ā¼ Data Warehouse Design and Usage
ā¼ Data Warehouse Implementation
ā¼ Data Generalization by Attribute-Oriented
Induction
ā¼ Summary
3. 3
What is a 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
4. 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. 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. 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. 7
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
8. 8
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
detailed, flat relational
isolated
historical,
summarized, multidimensional
integrated, consolidated
usage repetitive ad-hoc
access read/write
index/hash on prim. key
lots of scans
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
9. 9
Why a 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 relational databases
10. 10
Data Warehouse: A Multi-Tiered Architecture
Data
Warehouse
Extract
Transform
Load
Refresh
OLAP Engine
Analysis
Query
Reports
Data mining
Monitor
&
Integrator
Metadata
Data Sources Front-End Tools
Serve
Data Marts
Operational
DBs
Other
sources
Data Storage
OLAP Server
11. 11
Three Data Warehouse Models
ā¼ Enterprise warehouse
ā¼ collects all of the information about subjects spanning
the entire organization
ā¼ Data Mart
ā¼ a subset of corporate-wide data that is of value to a
specific groups of users. Its scope is confined to
specific, selected groups, such as marketing data mart
ā¼ Independent vs. dependent (directly from warehouse) data mart
ā¼ Virtual warehouse
ā¼ A set of views over operational databases
ā¼ Only some of the possible summary views may be
materialized
12. 12
Extraction, Transformation, and Loading (ETL)
ā¼ Data extraction
ā¼ get data from multiple, heterogeneous, and external
sources
ā¼ Data cleaning
ā¼ detect errors in the data and rectify them when possible
ā¼ Data transformation
ā¼ 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
13. 13
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
ā¼ warehouse schema, view and derived data definitions
ā¼ Business data
ā¼ business terms and definitions, ownership of data, charging policies
14. 14
Chapter 4: Data Warehousing and On-line
Analytical Processing
ā¼ Data Warehouse: Basic Concepts
ā¼ Data Warehouse Modeling: Data Cube and OLAP
ā¼ Data Warehouse Design and Usage
ā¼ Data Warehouse Implementation
ā¼ Data Generalization by Attribute-Oriented
Induction
ā¼ Summary
15. 15
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.
16. 16
Cube: A Lattice of Cuboids
time,item
time,item,location
time, item, location, supplier
all
time item location supplier
time,location
time,supplier
item,location
item,supplier
location,supplier
time,item,supplier
time,location,supplier
item,location,supplier
0-D (apex) cuboid
1-D cuboids
2-D cuboids
3-D cuboids
4-D (base) cuboid
17. 17
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
18. 18
Example of Star Schema
time_key
day
day_of_the_week
month
quarter
year
time
location_key
street
city
state_or_province
country
location
Sales Fact Table
time_key
item_key
branch_key
location_key
units_sold
dollars_sold
avg_sales
Measures
item_key
item_name
brand
type
supplier_type
item
branch_key
branch_name
branch_type
branch
19. 19
Example of Snowflake Schema
time_key
day
day_of_the_week
month
quarter
year
time
location_key
street
city_key
location
Sales Fact Table
time_key
item_key
branch_key
location_key
units_sold
dollars_sold
avg_sales
Measures
item_key
item_name
brand
type
supplier_key
item
branch_key
branch_name
branch_type
branch
supplier_key
supplier_type
supplier
city_key
city
state_or_province
country
city
20. 20
Example of Fact Constellation
time_key
day
day_of_the_week
month
quarter
year
time
location_key
street
city
province_or_state
country
location
Sales Fact Table
time_key
item_key
branch_key
location_key
units_sold
dollars_sold
avg_sales
Measures
item_key
item_name
brand
type
supplier_type
item
branch_key
branch_name
branch_type
branch
Shipping Fact Table
time_key
item_key
shipper_key
from_location
to_location
dollars_cost
units_shipped
shipper_key
shipper_name
location_key
shipper_type
shipper
21. 21
A Concept Hierarchy:
Dimension (location)
all
Europe North_America
MexicoCanadaSpainGermany
Vancouver
M. WindL. Chan
...
......
... ...
...
all
region
office
country
TorontoFrankfurtcity
22. 22
Data Cube Measures: Three Categories
ā¼ 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 partitioning
ā¼ 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 aggregate
function
ā¼ E.g., avg(), min_N(), standard_deviation()
ā¼ Holistic: if there is no constant bound on the storage size
needed to describe a subaggregate.
ā¼ E.g., median(), mode(), rank()
23. 23
View of Warehouses and Hierarchies
Specification of hierarchies
ā¼ Schema hierarchy
day < {month <
quarter; week} < year
ā¼ Set_grouping hierarchy
{1..10} < inexpensive
24. 24
Multidimensional Data
ā¼ Sales volume as a function of product, month,
and region
Product
Month
Dimensions: Product, Location, Time
Hierarchical summarization paths
Industry Region Year
Category Country Quarter
Product City Month Week
Office Day
25. 25
A Sample Data Cube
Total annual sales
of TVs in U.S.A.Date
Country
sum
sum
TV
VCR
PC
1Qtr 2Qtr 3Qtr 4Qtr
U.S.A
Canada
Mexico
sum
26. 26
Cuboids Corresponding to the Cube
all
product date country
product,date product,country date, country
product, date, country
0-D (apex) cuboid
1-D cuboids
2-D cuboids
3-D (base) cuboid
27. 27
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)
29. 29
A Star-Net Query Model
Shipping Method
AIR-EXPRESS
TRUCK
ORDER
Customer Orders
CONTRACTS
Customer
Product
PRODUCT GROUP
PRODUCT LINE
PRODUCT ITEM
SALES PERSON
DISTRICT
DIVISION
OrganizationPromotion
CITY
COUNTRY
REGION
Location
DAILYQTRLYANNUALY
Time
Each circle is
called a footprint
30. 30
Browsing a Data Cube
ā¼ Visualization
ā¼ OLAP capabilities
ā¼ Interactive manipulation
31. 31
Chapter 4: Data Warehousing and On-line
Analytical Processing
ā¼ Data Warehouse: Basic Concepts
ā¼ Data Warehouse Modeling: Data Cube and OLAP
ā¼ Data Warehouse Design and Usage
ā¼ Data Warehouse Implementation
ā¼ Data Generalization by Attribute-Oriented
Induction
ā¼ Summary
32. 32
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
33. 33
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
34. 34
Data Warehouse Development:
A Recommended Approach
Define a high-level corporate data model
Data
Mart
Data
Mart
Distributed
Data Marts
Multi-Tier Data
Warehouse
Enterprise
Data
Warehouse
Model refinementModel refinement
35. 35
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
36. 36
From On-Line Analytical Processing (OLAP)
to On Line Analytical Mining (OLAM)
ā¼ Why online analytical mining?
ā¼ High quality of data in data warehouses
ā¼ DW contains integrated, consistent, cleaned data
ā¼ Available information processing structure surrounding
data warehouses
ā¼ ODBC, OLEDB, Web accessing, service facilities,
reporting and OLAP tools
ā¼ OLAP-based exploratory data analysis
ā¼ Mining with drilling, dicing, pivoting, etc.
ā¼ On-line selection of data mining functions
ā¼ Integration and swapping of multiple mining
functions, algorithms, and tasks
37. 37
Chapter 4: Data Warehousing and On-line
Analytical Processing
ā¼ Data Warehouse: Basic Concepts
ā¼ Data Warehouse Modeling: Data Cube and OLAP
ā¼ Data Warehouse Design and Usage
ā¼ Data Warehouse Implementation
ā¼ Data Generalization by Attribute-Oriented
Induction
ā¼ Summary
38. 38
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?
ā¼ Materialization of data cube
ā¼ Materialize every (cuboid) (full materialization),
none (no materialization), or some (partial
materialization)
ā¼ Selection of which cuboids to materialize
ā¼ Based on size, sharing, access frequency, etc.
)1
1
( +ļ
=
=
n
i
iLT
39. 39
The āCompute Cubeā Operator
ā¼ 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
ā¼ Need compute the following Group-Bys
(date, product, customer),
(date,product),(date, customer), (product, customer),
(date), (product), (customer)
()
(item)(city)
()
(year)
(city, item) (city, year) (item, year)
(city, item, year)
40. 40
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
ā¼ A recent bit compression technique, Word-Aligned Hybrid (WAH),
makes it work for high cardinality domain as well [Wu, et al. TODSā06]
Cust Region Type
C1 Asia Retail
C2 Europe Dealer
C3 Asia Dealer
C4 America Retail
C5 Europe Dealer
RecID Retail Dealer
1 1 0
2 0 1
3 0 1
4 1 0
5 0 1
RecIDAsia Europe America
1 1 0 0
2 0 1 0
3 1 0 0
4 0 0 1
5 0 1 0
Base table Index on Region Index on Type
41. 41
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
42. 42
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?
ā¼ Explore indexing structures and compressed vs. dense array structs in MOLAP
43. 43
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
44. 44
Chapter 4: Data Warehousing and On-line
Analytical Processing
ā¼ Data Warehouse: Basic Concepts
ā¼ Data Warehouse Modeling: Data Cube and OLAP
ā¼ Data Warehouse Design and Usage
ā¼ Data Warehouse Implementation
ā¼ Data Generalization by Attribute-Oriented
Induction
ā¼ Summary
45. 45
Attribute-Oriented Induction
ā¼ Proposed in 1989 (KDD ā89 workshop)
ā¼ Not confined to categorical data nor particular measures
ā¼ How it is done?
ā¼ Collect the task-relevant data (initial relation) using a
relational database query
ā¼ Perform generalization by attribute removal or
attribute generalization
ā¼ Apply aggregation by merging identical, generalized
tuples and accumulating their respective counts
ā¼ Interaction with users for knowledge presentation
46. 46
Attribute-Oriented Induction: An Example
Example: Describe general characteristics of graduate
students in the University database
ā¼ Step 1. Fetch relevant set of data using an SQL
statement, e.g.,
Select * (i.e., name, gender, major, birth_place,
birth_date, residence, phone#, gpa)
from student
where student_status in {āMscā, āMBAā, āPhDā }
ā¼ Step 2. Perform attribute-oriented induction
ā¼ Step 3. Present results in generalized relation, cross-tab,
or rule forms
47. 47
Class Characterization: An Example
Name Gender Major Birth-Place Birth_date Residence Phone # GPA
Jim
Woodman
M CS Vancouver,BC,
Canada
8-12-76 3511 Main St.,
Richmond
687-4598 3.67
Scott
Lachance
M CS Montreal, Que,
Canada
28-7-75 345 1st Ave.,
Richmond
253-9106 3.70
Laura Lee
ā¦
F
ā¦
Physics
ā¦
Seattle, WA, USA
ā¦
25-8-70
ā¦
125 Austin Ave.,
Burnaby
ā¦
420-5232
ā¦
3.83
ā¦
Removed Retained Sci,Eng,
Bus
Country Age range City Removed Excl,
VG,..
Gender Major Birth_region Age_range Residence GPA Count
M Science Canada 20-25 Richmond Very-good 16
F Science Foreign 25-30 Burnaby Excellent 22
ā¦ ā¦ ā¦ ā¦ ā¦ ā¦ ā¦
Birth_Region
Gender
Canada Foreign Total
M 16 14 30
F 10 22 32
Total 26 36 62
Prime
Generalized
Relation
Initial
Relation
48. 48
Basic Principles of Attribute-Oriented Induction
ā¼ Data focusing: task-relevant data, including dimensions,
and the result is the initial relation
ā¼ Attribute-removal: remove attribute A if there is a large set
of distinct values for A but (1) there is no generalization
operator on A, or (2) Aās higher level concepts are
expressed in terms of other attributes
ā¼ Attribute-generalization: If there is a large set of distinct
values for A, and there exists a set of generalization
operators on A, then select an operator and generalize A
ā¼ Attribute-threshold control: typical 2-8, specified/default
ā¼ Generalized relation threshold control: control the final
relation/rule size
49. 49
Attribute-Oriented Induction: Basic
Algorithm
ā¼ InitialRel: Query processing of task-relevant data, deriving
the initial relation.
ā¼ PreGen: Based on the analysis of the number of distinct
values in each attribute, determine generalization plan for
each attribute: removal? or how high to generalize?
ā¼ PrimeGen: Based on the PreGen plan, perform
generalization to the right level to derive a āprime
generalized relationā, accumulating the counts.
ā¼ Presentation: User interaction: (1) adjust levels by drilling,
(2) pivoting, (3) mapping into rules, cross tabs,
visualization presentations.
50. 50
Presentation of Generalized Results
ā¼ Generalized relation:
ā¼ Relations where some or all attributes are generalized, with counts
or other aggregation values accumulated.
ā¼ Cross tabulation:
ā¼ Mapping results into cross tabulation form (similar to contingency
tables).
ā¼ Visualization techniques:
ā¼ Pie charts, bar charts, curves, cubes, and other visual forms.
ā¼ Quantitative characteristic rules:
ā¼ Mapping generalized result into characteristic rules with quantitative
information associated with it, e.g.,
.%]47:["")(_%]53:["")(_
)()(
tforeignxregionbirthtCanadaxregionbirth
xmalexgrad
=ļ=
ļļ
51. 51
Mining Class Comparisons
ā¼ Comparison: Comparing two or more classes
ā¼ Method:
ā¼ Partition the set of relevant data into the target class and the
contrasting class(es)
ā¼ Generalize both classes to the same high level concepts
ā¼ Compare tuples with the same high level descriptions
ā¼ Present for every tuple its description and two measures
ā¼ support - distribution within single class
ā¼ comparison - distribution between classes
ā¼ Highlight the tuples with strong discriminant features
ā¼ Relevance Analysis:
ā¼ Find attributes (features) which best distinguish different classes
52. 52
Concept Description vs. Cube-Based OLAP
ā¼ Similarity:
ā¼ Data generalization
ā¼ Presentation of data summarization at multiple levels of
abstraction
ā¼ Interactive drilling, pivoting, slicing and dicing
ā¼ Differences:
ā¼ OLAP has systematic preprocessing, query independent,
and can drill down to rather low level
ā¼ AOI has automated desired level allocation, and may
perform dimension relevance analysis/ranking when
there are many relevant dimensions
ā¼ AOI works on the data which are not in relational forms
53. 53
Chapter 4: Data Warehousing and On-line
Analytical Processing
ā¼ Data Warehouse: Basic Concepts
ā¼ Data Warehouse Modeling: Data Cube and OLAP
ā¼ Data Warehouse Design and Usage
ā¼ Data Warehouse Implementation
ā¼ Data Generalization by Attribute-Oriented
Induction
ā¼ Summary
54. 54
Summary
ā¼ Data warehousing: A multi-dimensional model of a data warehouse
ā¼ A data cube consists of dimensions & measures
ā¼ Star schema, snowflake schema, fact constellations
ā¼ OLAP operations: drilling, rolling, slicing, dicing and pivoting
ā¼ Data Warehouse Architecture, Design, and Usage
ā¼ Multi-tiered architecture
ā¼ Business analysis design framework
ā¼ Information processing, analytical processing, data mining, OLAM (Online
Analytical Mining)
ā¼ Implementation: Efficient computation of data cubes
ā¼ Partial vs. full vs. no materialization
ā¼ Indexing OALP data: Bitmap index and join index
ā¼ OLAP query processing
ā¼ OLAP servers: ROLAP, MOLAP, HOLAP
ā¼ Data generalization: Attribute-oriented induction
55. 55
References (I)
ā¼ S. Agarwal, R. Agrawal, P. M. Deshpande, A. Gupta, J. F. Naughton, R. Ramakrishnan, and S.
Sarawagi. On the computation of multidimensional aggregates. VLDBā96
ā¼ D. Agrawal, A. E. Abbadi, A. Singh, and T. Yurek. Efficient view maintenance in data
warehouses. SIGMODā97
ā¼ R. Agrawal, A. Gupta, and S. Sarawagi. Modeling multidimensional databases. ICDEā97
ā¼ S. Chaudhuri and U. Dayal. An overview of data warehousing and OLAP technology. ACM
SIGMOD Record, 26:65-74, 1997
ā¼ E. F. Codd, S. B. Codd, and C. T. Salley. Beyond decision support. Computer World, 27, July
1993.
ā¼ J. Gray, et al. Data cube: A relational aggregation operator generalizing group-by, cross-tab
and sub-totals. Data Mining and Knowledge Discovery, 1:29-54, 1997.
ā¼ A. Gupta and I. S. Mumick. Materialized Views: Techniques, Implementations, and
Applications. MIT Press, 1999.
ā¼ J. Han. Towards on-line analytical mining in large databases. ACM SIGMOD Record, 27:97-107,
1998.
ā¼ V. Harinarayan, A. Rajaraman, and J. D. Ullman. Implementing data cubes efficiently.
SIGMODā96
ā¼ J. Hellerstein, P. Haas, and H. Wang. Online aggregation. SIGMOD'97
56. 56
References (II)
ā¼ C. Imhoff, N. Galemmo, and J. G. Geiger. Mastering Data Warehouse Design: Relational and
Dimensional Techniques. John Wiley, 2003
ā¼ W. H. Inmon. Building the Data Warehouse. John Wiley, 1996
ā¼ R. Kimball and M. Ross. The Data Warehouse Toolkit: The Complete Guide to Dimensional
Modeling. 2ed. John Wiley, 2002
ā¼ P. OāNeil and G. Graefe. Multi-table joins through bitmapped join indices. SIGMOD Record, 24:8ā
11, Sept. 1995.
ā¼ P. O'Neil and D. Quass. Improved query performance with variant indexes. SIGMOD'97
ā¼ Microsoft. OLEDB for OLAP programmer's reference version 1.0. In
http://www.microsoft.com/data/oledb/olap, 1998
ā¼ S. Sarawagi and M. Stonebraker. Efficient organization of large multidimensional arrays. ICDE'94
ā¼ A. Shoshani. OLAP and statistical databases: Similarities and differences. PODSā00.
ā¼ D. Srivastava, S. Dar, H. V. Jagadish, and A. V. Levy. Answering queries with aggregation using
views. VLDB'96
ā¼ P. Valduriez. Join indices. ACM Trans. Database Systems, 12:218-246, 1987.
ā¼ J. Widom. Research problems in data warehousing. CIKMā95
ā¼ K. Wu, E. Otoo, and A. Shoshani, Optimal Bitmap Indices with Efficient Compression, ACM Trans.
on Database Systems (TODS), 31(1): 1-38, 2006
58. 58
Compression of Bitmap Indices
ā¼ Bitmap indexes must be compressed to reduce I/O costs
and minimize CPU usageāmajority of the bits are 0ās
ā¼ Two compression schemes:
ā¼ Byte-aligned Bitmap Code (BBC)
ā¼ Word-Aligned Hybrid (WAH) code
ā¼ Time and space required to operate on compressed
bitmap is proportional to the total size of the bitmap
ā¼ Optimal on attributes of low cardinality as well as those of
high cardinality.
ā¼ WAH out performs BBC by about a factor of two