1 / 16

vs. OLAP

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

kyran
Télécharger la présentation

vs. OLAP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. vs. OLAP

  2. Star Scheme Salescampaigns Salesorganization Time Sales, profit,costs, keynumbers, etc. Geography heirarchy Products Other dimension

  3. Salescampaigns Salesorganization Time Salesorganization Time Sales, profit,costs, keynumbers, etc. Geography heirarchy Products Geography heirarchy Products Other dimension Other dimension Other dimension Snowflake Scheme

  4. Salescampaigns Salesorganization Time Salesorganization Time Sales, profit,costs, keynumbers, etc. Geography heirarchy Products Geography heirarchy Products Other dimension Other dimension Other dimension Data Warehouse

  5. User Interface SQL queries are generated graphically. Flexible, but neither fast nor user-friendly. Data Warehouse Relational OLAP

  6. User Interface Every click is a query. Fast, but not flexible. Limited number of dimensions. Hyper Cube Build the cube. Lots of Data. Slow. Everything must be predefined. Data Warehouse Multidimensional OLAP

  7. User Interface Every click is a query. Fast, but not flexible. Limited number of dimensions. Hyper Cube Drill-through when needed. Slow, and not user-friendly. Data Warehouse Hybrid OLAP

  8. User Interface Data Warehouse QlikView file

  9. User Interface Relational database inside QlikView document. Data Warehouse is not required. Any data source will do. Data Warehouse QlikView file

  10. User Interface Load the data… Data Source QlikView file then work off-line!

  11. User Interface QlikView file

  12. User Interface Every click is a query. Extremely fast, and very flexible. Click ! The selection propagates through the relational database. The technology used is called AQL.

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

  14. User Interface 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.

  15. Summary • MOLAP • Limited number of dimensions • Not Flexible • ROLAP • Not User-friendly • HOLAP • A poor combination of the two above methods

  16. Summary • Data warehouse not necessary • Unlimited number of dimensions • Possibility for several hypercubes talking to each other • Flexible • User-Friendly

More Related