16
vs. OLAP

Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Embed Size (px)

Citation preview

Page 1: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

vs.

OLAP

Page 2: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Geographyheirarchy

Salescampaigns

Other dimension

Products

Time

Sales, profit,costs, key

numbers, etc.

Salesorganization

Star Scheme

Henrik Been
The star sheme is a common structure for storing data. Measures are stored in a central fact table surrounded by dimension tables.
Page 3: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Snowflake Scheme

Geographyheirarchy

Salescampaigns

Other dimension

Products

Time

Sales, profit,costs, key

numbers, etc.

Salesorganization

Products

Time

Other dimension

Other dimension

Geographyheirarchy

Salesorganization

Henrik Been
A snowflake scheme is basically
Page 4: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Data Warehouse

Geographyheirarchy

Salescampaigns

Other dimension

Products

Time

Sales, profit,costs, key

numbers, etc.

Salesorganization

Products

Time

Other dimension

Other dimension

Geographyheirarchy

Salesorganization

Page 5: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Relational OLAP

Data Warehouse

SQL queries are generated graphically. Flexible, but neither fast nor user-friendly.

User Interface

Page 6: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Multidimensional OLAP

Data Warehouse

User Interface

Hyper CubeBuild the cube. Lots of Data. Slow. Everything must be predefined.

Every click is a query. Fast, but not flexible. Limited number of dimensions.

Page 7: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Hybrid OLAP

Data Warehouse

User Interface

Hyper Cube

Every click is a query. Fast, but not flexible. Limited number of dimensions.

Drill-through when needed. Slow, and not user-friendly.

Page 8: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Data Warehouse

User Interface

QlikView file

Page 9: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Relational database inside QlikView document.

Data Warehouse

User Interface

QlikView file

Data Warehouse is not required. Any data source will do.

Page 10: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Data Source

User Interface

QlikView file

Load the data… then work off-line!

Page 11: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

User Interface

QlikView file

Page 12: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Every click is a query. Extremely fast, and very flexible.

Click !

The selection propagates through the relational database. The technology used is called AQL.

User Interface

Page 13: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

AQL™ The patented AQL technology performs its associations when a QlikView user makes a query through the point-and-click interface.

As a value or several values (in a dimension) are selected, QlikView makes a split second association showing only values (in other dimensions and measures) associated with the current selection.

Simultaneously, graphs and tables (holding one or several general expressions), are calculated to show the result of the current selection.

Page 14: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

Any number of Virtual hypercubes (Pivot tables, Diagrams, Gauges etc.) can be put in the QlikView document.

These are calculated on demand, i.e. on every click.

User Interface

Page 15: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

• MOLAP– Limited number of dimensions– Not Flexible

• ROLAP– Not User-friendly

• HOLAP– A poor combination of the two above methods

Summary

Page 16: Vs. OLAP. Geography heirarchy Sales campaigns Other dimension Products Time Sales, profit, costs, key numbers, etc. Sales organization Star Scheme

• Data warehouse not necessary• Unlimited number of dimensions• Possibility for several hypercubes talking to

each other• Flexible• User-Friendly

Summary