Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreShape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.
I'm creating an OData v4 feed that currently contains one entity set. This entity set contains around 1 million records with only five columns (of respective types int64, datetime, datetime, string, and string).
When loading this OData feed into PowerBI desktop (2.50.4859.502 64-bit September, 2017), it becomes terribly slow when the initial load is done and PowerBI is hardly workable.
Filtering is not truly an option, because I need all data of the mentioned entity set. Currently, the entity OData URL returns 50,000 records a time, with a `$skip` link to the next 50,000 records. Is there any OData v4 feature out there to make this feed work nicely in PowerBI?
And, on a side-note: would loading this same data into Azure Table Storage perform better within PowerBI?
We can't do too much from Power BI side to optimize when retrieving such a big dataset.
I suggest you loading data from Azure storage so that you can use Direct Query. But it has 1 millon records limitation. For more details, please see: Use DirectQuery in Power BI Desktop
Regards,
User | Count |
---|---|
93 | |
92 | |
85 | |
83 | |
49 |
User | Count |
---|---|
150 | |
142 | |
112 | |
73 | |
55 |