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!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi ,
I have a "large dataset" formatted dataset that is apprx 10 gb and growing which is hitting memory constraints even with incremental refresh enabled on a P1 SKU on a import model.
I am looking at exploring options on reducing dataset size.
Is there a way to use hybrid tables inverted so that historical data is in direct query mode and current data is in Import mode?
That would fit my needs since historical will be sparsely used and I dont need "real time" levels of latency. So looking at caching new data for performance.
Alternatively, Can the same be achieved using composite models or any other ideas?
Thanks,
Anand
Hi @AnandGNR,
In fact, direct query not suitable to handle that stores large amount of records. They will exceed to the limit when use table fields on visual.
Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn
I'd like to suggest you split these records to two dataset and one used to store these historical data and you create a report with multiple datasets.
Regards,
Xiaoxin Sheng
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |