Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
6 | |
6 | |
3 | |
2 | |
2 |