Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
Hi-
I'm working on a large data project with multiple fact tables that need at least 2 years of data. Fact tables are 40 mill rows + per table per year with 20+ dimension tables
Some of the aggregate tables I am working with are not shrinking the row count that much. Would partitioning the Aggregate table help to increase our end user speed? Is that possible?
We are already (1) query folding using native query Value.NativeQuery(Database,
Does "groupby" have to happen in both the SQL query AND the MQuery to make sure the aggregate gets folded back ?
Hi @sailkitty5 : can you share the size of the semantic model and whats the database you are using .
What is the response time that you are expecting ? it depends upon the visual and underlying dax too..
40 million rows per year is not a huge data, you can still implement incremental refresh on the fact table and import it .
if you can share more details on this the community can help better .
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 6 | |
| 6 | |
| 6 |