The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hi,
We currently have a P1 premium capacity. We are utilising deployment pipelines within our capacity resulting in environment workspaces (DEV and TEST) sometimes containing unwanted capacity draining resources. We purchased some PPU licenses to isolate these troublesom workspaces but without usage metrics on the PPU workspaces it was hard to determine if these would again cause issues moving back into our premium capacity or not. Is the best strategy to purchase another P1 capacity for DEV and TEST content so the PROD capacity isn't effected or would a P2 be enough here? Any other options?
Thanks.
Solved! Go to Solution.
You can split a P2 into two P1 but then you end up having the same performance issues again. A better approach (if you can afford it) is to use two or more P2 or higher. For example our Finance team has a dedicated P4 for production and a P3 as Dev/DR.
P2 has double the capacity of a P1.
And yes, getting extra P1s (at the minimum) is the right thing to do if you can afford it.
Thanks for your reply. Can a P2 be split to keep Dev and Test workspaces away from Prod?
You can split a P2 into two P1 but then you end up having the same performance issues again. A better approach (if you can afford it) is to use two or more P2 or higher. For example our Finance team has a dedicated P4 for production and a P3 as Dev/DR.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
52 | |
26 | |
14 | |
14 | |
12 |
User | Count |
---|---|
107 | |
38 | |
25 | |
23 | |
19 |