Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi,
I'm facing a problem while trying to get data from "OData Connector", trying to get a 100M+ rows dataset.
After 45M rows loaded my RAM is overloaded (see screenshot).
How to analyze a high volumetry dataset ? (looking for both free and paid options)
in memory overload
Regards,
Adry
Solved! Go to Solution.
You can try to use Direct Query instead of Import mode, or try to add extra memory for your computer.
Best Regards,
Herbert
In order to reduce the amount of RAM your Data Model uses you must consider casting the columns to the appropriate data types. Very often a forgotten text column which actually represents a number would consume all of your RAM in no time.
Also worth mentioning that the data types that you have in your data model are not necessary reflective of those that you get in your query. That is why checking how your data is structured in your Data Model is a quick win for RAM consumption.
Secondly, depending from where you get your data from you consider changin your M Query. The quick wins here are streaming the data or if you are making any intensive calculations in your queries Buffer the intermediarry steps.
And finally consider loading the data one query at a time.
In order to reduce the amount of RAM your Data Model uses you must consider casting the columns to the appropriate data types. Very often a forgotten text column which actually represents a number would consume all of your RAM in no time.
Also worth mentioning that the data types that you have in your data model are not necessary reflective of those that you get in your query. That is why checking how your data is structured in your Data Model is a quick win for RAM consumption.
Secondly, depending from where you get your data from you consider changin your M Query. The quick wins here are streaming the data or if you are making any intensive calculations in your queries Buffer the intermediarry steps.
And finally consider loading the data one query at a time.
You can try to use Direct Query instead of Import mode, or try to add extra memory for your computer.
Best Regards,
Herbert
Thanks for the tips
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
59 | |
53 | |
52 | |
36 | |
33 |
User | Count |
---|---|
80 | |
73 | |
45 | |
45 | |
43 |