Lecture 2 PPTs.ppt

7/27/2019 Lecture 2 PPTs.ppt

1/35

1

PGDM : BI

LECTURE-3


2/35

2

What is Data Warehouse?

Defined in many different ways, but not rigorously.

A decision support database that is maintainedseparately from the organizations operationaldatabase

Support information processing by providing a solidplatform of consolidated, historical data for analysis.

A data warehouse is asubject-oriented, integrated,time-variant, and nonvolatilecollection of data in support

of managements decision-making process.W. H.Inmon

Data warehousing:

The process of constructing and using data

warehouses


3/35

3

Data WarehouseSubject-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 particularsubject issues by excluding data that are not useful in

the decision support process.


4/35

4

Data WarehouseIntegrated

Constructed by integrating multiple, heterogeneousdata sources

relational databases, flat files, on-line transactionrecords

Data cleaning and data integration techniques areapplied.

Ensure consistency in naming conventions, encodingstructures, attribute measures, etc. among different

data sources E.g., Hotel price: currency, tax, breakfast covered, etc.

When data is moved to the warehouse, it isconverted.


5/35

5

Data WarehouseTime 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/35

6

Data WarehouseNon-Volatile

Aphysically separate store of data transformed from the

operational environment.

Operational update of data does not occur in the datawarehouse environment.

Does not require transaction processing, recovery,

and concurrency control mechanisms

Requires only two operations in data accessing:

initial loading of dataand access of data.


7/357

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 isused 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


8/358

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


9/359

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-datedetailed, 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


10/3510

Why Separate Data Warehouse?

High performance for both systems

DBMS tuned for OLTP: access methods, indexing,concurrency control, recovery

Warehousetuned for OLAP: complex OLAP queries,

multidimensional view, consolidation. Different functions and different data:

missing data: Decision support requires historical datawhich operational DBs do not typically maintain

data consolidation: DS requires consolidation(aggregation, summarization) of data fromheterogeneous sources

data quality: different sources typically useinconsistent data representations, codes and formats

which have to be reconciled


11/3511

From Tables and Spreadsheetsto 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.


12/3512

Cube: A Lattice of Cuboids

all

time item location supplier

time,item time,location

time,supplier

item,location

item,supplier

location,supplier

time,item,location

time,item,supplier

time,location,supplier

item,location,supplier

time, item, location, supplier

0-D(apex) cuboid

1-D cuboids

2-D cuboids

3-D cuboids

4-D(base) cuboid


13/3513

Conceptual Modeling ofData 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


14/3514

Example of Star Schema

time_key

day

day_of_the_week

month

quarter

year

time

location_key

streetcity

province_or_street

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_namebranch_type

branch


15/3515

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_solddollars_sold

avg_sales

Measures

item_key

item_name

brand

type

supplier_key

item

branch_key


branch

supplier_key

supplier_type

supplier

city_key

city

province_or_stree

country

city


16/3516

Example of Fact Constellation

time_key

day

day_of_the_week

month

quarter

year

time

location_key

streetcity

province_or_street

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

Shipping Fact Table

time_key

item_key

shipper_key

from_location

to_location

dollars_cost

units_shipped

shipper_key

shipper_name

location_keyshipper_type

shipper


17/3517

Data WarehousingDefinitions and Concepts

Data mart

A departmental data warehouse that stores onlyrelevant data

Dependent data martA subset that is created directly from a datawarehouse

Independent data mart

A small data warehouse designed for a strategicbusiness unit or a department


18/3518


Operational data stores (ODS)

A type of database often used as an interim areafor a data warehouse, especially for customer

information files Oper marts

An operational data mart. An oper mart is a small-scale data mart typically used by a singledepartment or functional area in an organization


19/3519


Enterprise data warehouse (EDW)

A technology thatprovides a vehicle for pushingdata from source systems into a data warehouse

MetadataData about data. In a data warehouse, metadatadescribe the contents of a data warehouse andthe manner of its use


20/3520

Data WarehousingProcess Overview


21/3521

Data WarehousingProcess Overview

The major components of a data warehousingprocess

Data sources

Data extraction Data loading

Comprehensive database

Metadata Middleware tools


22/3522

Data Warehousing Architectures

Three parts of the data warehouse

The data warehouse that contains the data andassociated software

Data acquisition (back-end) software thatextracts data from legacy systems and externalsources, consolidates and summarizes them,and loads them into the data warehouse

Client (front-end) software that allows users toaccess and analyze data from the warehouse


23/35

23



24/35

24



25/35

25



26/35

26



27/35

27



28/35

October 28, 2013 28

A Concept Hierarchy: Dimension (location)

all

Europe North_America

MexicoCanadaSpainGermany

Vancouver

M. WindL. Chan

...

......

... ...

...

all

region

office

country

TorontoFrankfurtcity


29/35

29

Multidimensional Data

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

Pro

duct

Month

Dimensions: Product, Location, Time

Hierarchical summarization paths

Industry Region Year

Category Country Quarter

Product City Month Week

Office Day


30/35

30

A Sample Data Cube

Total annual salesof TV in U.S.A.

Date

Countr

ysum

sumTV

VCRPC

1Qtr 2Qtr 3Qtr 4Qtr

U.S.A

Canada

Mexico

sum


31/35

31

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


32/35

32

Browsing a Data Cube

Visualization

OLAP capabilities

Interactive manipulation


33/35

33

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.


34/35

34

OLAP Server Architectures

Relational OLAP (ROLAP)

Use relational or extended-relational DBMS tostore and manage warehouse data and OLAP

middle ware to support missing pieces Multidimensional OLAP (MOLAP)

Array-based multidimensional storage engine

(sparse matrix techniques) Hybrid OLAP (HOLAP)

User flexibility, e.g., low level: relational, high-level: array


35/35

THANK YOU

Documents

Lecture 2 PPTs.ppt