This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowThe Fabric community is upgrading! Read all of the details including the timeline and what you can expect. Learn more
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
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
| User | Count |
|---|---|
| 13 | |
| 11 | |
| 9 | |
| 6 | |
| 5 |