4. Difficulties to decide – keep in mind…!
Power BI Solution Architecture – Decide before implementing
Import: Loading data
- Consuming memory & disk space
- Pros: Excellent performance model , fully functional!
- Lim: Max. 1-GB per file
DirectQuery: Connection to data source
- Visualization only
- But! Stores
- Pros: No data size issues , always current data
- Lim: Query size, single database , if Query Editor & DAX is complex
5. One Version of Truth
One dataset to maintain/share
Add ‘local’ measures
New experience workspaces
Power BI service live connection
Datasets across multiple workspaces
Datasets: Powerful or problematic…?
6. Dataflow is internally stored in a
Once per day
Once per month
Once per quarter
ETL
Collection of data - Dataflow
Power Query process that runs in the cloud – Connect, clean, transform, load
7. Common Data Model - CMD
Keep sharing & be efficient!!
One metadata definition
Connect & create
Better business decisions
8. Only one single table… Please don’t!
Modeling basics
0123456789
Descriptive information
Slice/dice data of fact table
DescriptiveFact
ProductKey UnitPrice OrderQuantity
999 1.00 4.00
CustomerKey FirstName BirthDate
999 Sharona 18-10-1995
9. Left or right…?
Relationship directions
Relationship
Filter data
Create visuals
Show insights Wrong Model!
Both-Directional relationships
Keep it simple!
Fast, efficient, understandable
Create relationships
Name properly
Choose data types
Filter irrelevant data
10. Findings & Insights - dataset
Power BI Report
Interactive information
Interactive visuals
Dig into data, discover
Customizable
Updated automatically when data changes
Safely explore & experiment