Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
HI All
Have a very special report, that uses a query in SAP BW, which is quite big. We already managed to somehow reduce the number of lines, but I think it is still big.
Current status is, that we are able to load 2 years of the data from SAP BW to PBI (impot mode), but there are still lot of rows - 70M rows (the load is quite fast only 2hours).
The question is, if you can estimate any performance for such big dataset, eventualy what to check? If you have any experience with such big dataset?
Currently the customer want only some 3 small tables, but in the future they want to extend the report. Report should run in Service, so any suggestion for consideration would be helpful.
Solved! Go to Solution.
@tomas12344 So import mode is going to be the fastest in terms of performance. The actual performance of the report will be mainly controlled by how many visuals you have on a page and how complex your DAX measures are. It is extremely difficult to know any of that until you actually create the report.
Hi @tomas12344 ,
Microsoft provides a comprehensive guide on optimizing Power BI solutions, including data model optimization, visualization optimization, and environment optimization. Please refer: Optimization guide for Power BI - Power BI | Microsoft Learn
In addition to this, incremental refresh allows you to load and refresh data in increments, significantly reducing load times and resource usage.
If you're not already, consider using Power BI Premium. It provides dedicated capacity which can handle larger datasets and more complex reports than the shared capacity.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello @tomas12344, for such an extraction you may have to split the load into multiple packets.
you will find these useful:
Microsoft recommended architecture for PowerBI / Fabric integration with SAP (See the cached method):
Questions? please reach out.
Anupam
Hi @tomas12344 ,
Microsoft provides a comprehensive guide on optimizing Power BI solutions, including data model optimization, visualization optimization, and environment optimization. Please refer: Optimization guide for Power BI - Power BI | Microsoft Learn
In addition to this, incremental refresh allows you to load and refresh data in increments, significantly reducing load times and resource usage.
If you're not already, consider using Power BI Premium. It provides dedicated capacity which can handle larger datasets and more complex reports than the shared capacity.
Best Regards,
Neeko Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello @tomas12344, for such an extraction you may have to split the load into multiple packets.
you will find these useful:
Microsoft recommended architecture for PowerBI / Fabric integration with SAP (See the cached method):
Questions? please reach out.
Anupam
@tomas12344 So import mode is going to be the fastest in terms of performance. The actual performance of the report will be mainly controlled by how many visuals you have on a page and how complex your DAX measures are. It is extremely difficult to know any of that until you actually create the report.
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 |
---|---|
76 | |
76 | |
56 | |
38 | |
34 |
User | Count |
---|---|
99 | |
56 | |
51 | |
44 | |
40 |