This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hello! We have started to get refresh errors regarding premium capacity being throttled. When we first started using Power BI, a decision was made to split our P2 node into two separate P1 nodes for better load balancing. Could anyone give me any advice as to whether it is better to have two separate P1 nodes or if we would have less errors if we went with a single P2 node? Thank you so much!
Solved! Go to Solution.
Hi @Anonymous ,
As mentioned by GilbertQ, it depends on your requirements. We always separating business critical and Self-Service BI (SSBI) into different capacities to prevent the situation where the report is stuck and need to wait. Please refer to https://docs.microsoft.com/en-us/power-bi/admin/service-premium-capacity-optimize
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Dedmon Dai
Hi @Anonymous ,
As mentioned by GilbertQ, it depends on your requirements. We always separating business critical and Self-Service BI (SSBI) into different capacities to prevent the situation where the report is stuck and need to wait. Please refer to https://docs.microsoft.com/en-us/power-bi/admin/service-premium-capacity-optimize
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Best Regards,
Dedmon Dai
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 7 | |
| 7 | |
| 6 |
| User | Count |
|---|---|
| 28 | |
| 24 | |
| 22 | |
| 22 | |
| 17 |