Dimensional Modeling, Schemes and Mind Maps of Business

The aggregated fact columns are the matter of the analysis. 13 / 48. Page 31. Dimension tables. • Each dimension table ...

Typology: Schemes and Mind Maps

2022/2023

Uploaded on 02/28/2023

ekaram
ekaram 🇺🇸

4.6

(30)

264 documents

1 / 163

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Dimensional Modeling
Krzysztof Dembczy´nski
Intelligent Decision Support Systems Laboratory (IDSS)
Pozna´n University of Technology, Poland
Bachelor studies, seventh semester
Academic year 2018/19 (winter semester)
1 / 48
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44
pf45
pf46
pf47
pf48
pf49
pf4a
pf4b
pf4c
pf4d
pf4e
pf4f
pf50
pf51
pf52
pf53
pf54
pf55
pf56
pf57
pf58
pf59
pf5a
pf5b
pf5c
pf5d
pf5e
pf5f
pf60
pf61
pf62
pf63
pf64

Partial preview of the text

Download Dimensional Modeling and more Schemes and Mind Maps Business in PDF only on Docsity!

Dimensional Modeling

Krzysztof Dembczy´nski

Intelligent Decision Support Systems Laboratory (IDSS) Pozna´n University of Technology, Poland

Bachelor studies, seventh semester Academic year 2018/19 (winter semester)

Review of the Previous Lecture

  • Processing of massive datasets.
  • Evolution of database systems: I (^) Operational (OLTP) vs. analytical (OLAP) systems. I (^) Analytical database systems. I (^) Design of data warehouses. I (^) Relational model vs. multidimensional model. I (^) NoSQL. I (^) Processing of massive datasets.

Outline

1 Motivation

2 Conceptual Schemes of Data Warehouses

3 Dimensional Modeling

4 Summary

Motivation

  • (^) University authorities decided to analyze teaching performance by using the data collected in databases owned by the university containing information about students, instructors, lectures, faculties, etc.

Motivation

  • (^) University authorities decided to analyze teaching performance by using the data collected in databases owned by the university containing information about students, instructors, lectures, faculties, etc.
  • They would like to get answers for the following queries:

Motivation

  • (^) University authorities decided to analyze teaching performance by using the data collected in databases owned by the university containing information about students, instructors, lectures, faculties, etc.
  • They would like to get answers for the following queries: I (^) What is the average score of students over academic years?

Motivation

  • (^) University authorities decided to analyze teaching performance by using the data collected in databases owned by the university containing information about students, instructors, lectures, faculties, etc.
  • They would like to get answers for the following queries: I (^) What is the average score of students over academic years? I (^) What is the number of students over academic years? I (^) What is the average score by faculties, instructors, etc.?

Motivation

  • (^) University authorities decided to analyze teaching performance by using the data collected in databases owned by the university containing information about students, instructors, lectures, faculties, etc.
  • They would like to get answers for the following queries: I (^) What is the average score of students over academic years? I (^) What is the number of students over academic years? I (^) What is the average score by faculties, instructors, etc.? I (^) What is the distribution of students over faculties, semesters, etc.?

Example

  • An exemplary query could be the following:

SELECT Instructor, Academic_year, AVG(Grade) FROM Data_Warehouse GROUP BY Instructor, Academic_year

  • And the result:

Academic year Name AVG(Grade) 2010/11 Stefanowski 4. 2011/12 Stefanowski 4. 2010/12 Slowi´nski 4. 2011/12 Slowi´nski 4. 2011/12 Dembczy´nski :)

Motivation

  • (^) Problem to solve: How to design a database for analytical queries?

Conceptual schemes of data warehouses

  • (^) Three main goals for logical design: I (^) Simplicity: - (^) Users should understand the design, - (^) Data model should match users’ conceptual model, - (^) Queries should be easy and intuitive to write. I (^) Expressiveness: - (^) Include enough information to answer all important queries, - Include all relevant data (without irrelevant data). I (^) Performance: - An efficient physical design should be possible to apply.

Three basic conceptual schemes

  • Star schema,
  • (^) Snowflake schema,
  • (^) Fact constellations.

Star schema

  • (^) Measures, e.g. grades, price, quantity.

Star schema

  • (^) Measures, e.g. grades, price, quantity. I (^) Measures should be aggregative.