Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have been reading https://powerbi.microsoft.com/en-us/documentation/reportserver-capacity-planning/
I was wondering why the "Report Server Database" server was sized so large ? It's larger than the PIB RS server in the small configuration.
Would it be possible to see the load test resutls for the "Report Server Database" server and the SSAS server in addition to the PBI RS Server?
I was considering putting the RS database on the same server as SSAS but I am wondering if it is realy a good idea.
Are you aware that the latest release of Power BI Report Servere comes with an embedded SSAS instance, simillar to the Power BI desktop architecture? Maybe that's why needs a greater capacity. It can become a bottleneck if the refresh of non direct-query reports are taking all of the memory resources with this embedded instance of SSAS.
Hi @pdeville,
From PG's response, they haven’t started the work for capacity planning yet. This is on their board. Currently, it might not possible to see the load test resutls for the "Report Server Database" server and the SSAS server.
Regards,
Yuliana Gu
Thanks for your answers.
The performance of Power BI and the end user exprience certainely depends on the performances of SSAS and the reports server database.
So having the test results for others servers in the farm would be very instresting.
Best regards.
Hi @pdeville,
Per my knowledge, the Report Server Database server needs to store many metadata and object definitions, so it needs enough space. But I am not sure about this.
For whether it is possible to see the load test resutls for the "Report Server Database" server and the SSAS server, I have emailed to PG to consult with them. Once I get any response, I will update here.
Regards,
Yuliana Gu
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
12 | |
6 | |
4 | |
3 | |
2 |
User | Count |
---|---|
13 | |
10 | |
5 | |
3 | |
3 |