Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
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
Solved! Go to Solution.
Hi @Rita2,
Power BI can handle large datasets, but Import mode is not suitable if data exceeds memory or refresh limits. For scenarios with very large datasets, such as 2 billion rows, DirectQuery or Hybrid mode is recommended. DirectQuery has a 1 million row limit per query and requires data aggregation, with performance depending on the source, so optimizing Trino is important. Microsoft recommends doing transformations, indexing, and pre-aggregation at the source for better performance. Wide tables with around 800 columns are supported, but visuals are limited to about 125 columns for large results, which can impact performance, so reducing columns and proper modeling are necessary. In Premium, some limits like row set size can be increased, but they must be managed according to the datasource and capacity to avoid performance issues.
DirectQuery in Power BI: When to Use, Limitations, Alternatives - Power BI | Microsoft Learn
Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
How to configure workloads in Power BI Premium - Microsoft Fabric | Microsoft Learn
Thank you.
Hi @Rita2,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you.
Hi @Rita2,
Have you had a chance to review the solution we shared earlier? If the issue persists, feel free to reply so we can help further.
Thank you.
Hi @Rita2,
Power BI can handle large datasets, but Import mode is not suitable if data exceeds memory or refresh limits. For scenarios with very large datasets, such as 2 billion rows, DirectQuery or Hybrid mode is recommended. DirectQuery has a 1 million row limit per query and requires data aggregation, with performance depending on the source, so optimizing Trino is important. Microsoft recommends doing transformations, indexing, and pre-aggregation at the source for better performance. Wide tables with around 800 columns are supported, but visuals are limited to about 125 columns for large results, which can impact performance, so reducing columns and proper modeling are necessary. In Premium, some limits like row set size can be increased, but they must be managed according to the datasource and capacity to avoid performance issues.
DirectQuery in Power BI: When to Use, Limitations, Alternatives - Power BI | Microsoft Learn
Use DirectQuery in Power BI Desktop - Power BI | Microsoft Learn
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
How to configure workloads in Power BI Premium - Microsoft Fabric | Microsoft Learn
Thank you.
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 |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |