Thanks for taking the time with this Adam. So so helpful - in regards to the variables that combine to decide on an appropriate Capacity - it would be great if the utilisation report held more historical usage and attempted to use predictive analysis for capacity planning (when a P2/P3 may be required with current growth.)
If I scale-up (in other words edit my capacity setting and go from a P1 to a P2 (assuming I have avaialble cores), what happens on the back-end? Does the service automatically perform the increase? Is there anything I need to move or is all that hidden from me?
How much capacity is required for paginated reports which hold approx 1M rows in Power BI embedded capacity?? Also can non-pro users are able to see the reports if included in the APP??
You mentioned in the video having 2 P1s and moving workspaces to the another P1 in order to free up space. What about if you’d like to merge both capacities? What would your approach be as Power BI doesn’t let you merge capacities automatically?
Move everything into one capacity then delete the empty capacity you moved things from. Assign the v-cores to the remaining capacity. Giggle as the dataset SKU limit chart in the metrics app jumps up (the CPU limit won't move, because it's always 100% of whatever the SKU limit is at the time) Do this all out of hours to avoid overloading the P1 in the short space between moving workspaces into it and assigning the recovered v-cores from the other capacity. Or do it live, that's fun too.
Great video!! But I have one question running in my mind from long time For example we have an import model report which has a size of 10MB. There are 10 visuals which mostly have sum measures Will the premium at highest capacity be able to handle 5000 concurrent users?
Thanks for the reply Bharath As I need to share the report to thousands of users, I need premium right? Even if I opt for pro, all the users who want to view the report should have pro, right? Am I missing something here?
