Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Is it necessary to use the same capacities for the Development and Production environment?
Solved! Go to Solution.
HI @FerryTechnical , the topic of Fabric Capacity administration is extremely interesting and you’ll find plenty of recommended patterns out there. Ultimately, you need to choose the one that best fits your needs from two key perspectives: technical and financial. Let me start by addressing your question…
The answer is No, quite the opposite in fact! It is STRONGLY SUGGESTED to separate Dev from Prod capacities for these reasons:
I think this MSFT article tackles quite nicely Plan your Microsoft Fabric capacity: Strategic guide overview all you need to know, in particular to support your question, I think part 2 is particularly useful.
Well, ther you go, the topic is quite extensive so, if you have additional questions, reach out! I would appreciate a thumbs-up and you accept this as solution to your question ... all the best
Hi @FerryTechnical,
As others have mentioned, you should ideally use seperate capacities so that you don't accidently blow up production.
I've also found that forcing development work to be on smaller capacities like an F4 or F8 pushes developers to be more efficient as if they are not efficient they blow up their dev environment.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Proud to be a Super User! | |
HI @FerryTechnical , the topic of Fabric Capacity administration is extremely interesting and you’ll find plenty of recommended patterns out there. Ultimately, you need to choose the one that best fits your needs from two key perspectives: technical and financial. Let me start by addressing your question…
The answer is No, quite the opposite in fact! It is STRONGLY SUGGESTED to separate Dev from Prod capacities for these reasons:
I think this MSFT article tackles quite nicely Plan your Microsoft Fabric capacity: Strategic guide overview all you need to know, in particular to support your question, I think part 2 is particularly useful.
Well, ther you go, the topic is quite extensive so, if you have additional questions, reach out! I would appreciate a thumbs-up and you accept this as solution to your question ... all the best
Hi @FerryTechnical, typically dev capacities are smaller than Prod capacities since you usually work with smaller data sets, just big enough to test functionality.
Depending on the size of your project and company + team and working hours you can even pause your dev/test capacities when not in use to further cut down on costs.
No, it is actually better to use a different capacity for your production environment, you don't want issues in Dev/Test to affect your end users!
For more info, please watch my video on capacity management:
https://youtu.be/SmQ7FqMu0No?si=ktd7iolIXuJUV3vA
--------------------------------
I hope this helps, please give kudos and mark as solved if it does!
Connect with me on LinkedIn.
Subscribe to my YouTube channel for Fabric/Power Platform related content!
Hi @wardy912 I justed to say that I saw your video explaining capacities and I LIKED IT SO MUCH! It was an amazing work putting togheter so much useful information, I'll using as a reference moving forward ... BIG THANKS and kudos to you mate 😁 ... all the very best.
Thank you @svenchio,
really glad you found it useful, more coming in the new year!
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 13 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
| User | Count |
|---|---|
| 22 | |
| 20 | |
| 14 | |
| 12 | |
| 12 |