Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
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,
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 63 | |
| 32 | |
| 31 | |
| 25 |