March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch 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)
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
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
133 | |
91 | |
88 | |
64 | |
58 |
User | Count |
---|---|
201 | |
137 | |
107 | |
73 | |
68 |