Deep dive into Hybrid

Tables in Power BI
Asanka Padmakumara
Asanka Padmakumara
• Technical Lead Consultant - Qrious
• Blog: asankap.wordpress.com
• Linked In:
linkedin.com/in/asankapadmakumara
• Twitter: @asanka_e
Import vs Direct Query

Direct
Query Hybrid
Tables
Latency

Import

Performance
How does Hybrid Tables work?

Import/ Incremental Refresh

Direct Query
Import Direct Query Partition

Import/Archive Data
What Hybrid Tables offer?
• Fast in-memory base performance
• Up to date data with direct query
• Less resource utilisation in the capacity
• In-built incremental refresh
• Allow to work on large datasets
Limitations
• Only Available in Embedded, PPU or Premium Capacity
• Currently in preview
• Can not use with complex M-Query Transformations
• Possible performance issues
• Can not download the pbix file from service
Scenario #1
Incremental refresh for 5 Days data, Archive after 5 years

Between 2021/07/17-2022/07/21
Import/ Incremental Refresh

Direct Query
2022/07/22 and later
Import/ Archived Data

After 2022/07/17 and before 2017/07/22

Scenario #2

Import/ Cold Data

Before 2021/01/01

Direct Query/ Hot Data

1/01/2022 and later
Scenario #3

Direct Query/ Old Data

Before 2017/01/01

Import/ New Data

1/01/2017 and later
Scenario #4

Import/ less critical Data

Rest of the regions

Direct/ Critical Data

North America Region
Things we can’t do
• Real time with direct query, Increment refresh policy and direct query
on historical data
• There can only be one Direct Query partition
Best Practices
• Start with Direct Query, then convert to Import
• Only use with large Fact tables
• Set connecting dimensions to Duel mode
Q&A