Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hello,
I had A1 Capacity initially as my Power BI file was 3 GB. We weren't able to refresh the file in the workspace with A1 Capacity. Hence, we scaled up the capacity to A4 and we were able to refresh the 3 GB dataset.
Then, we scaled down the capacity back to A1.
After scaling down the capacity to A1, I published a file of 250 MB to that same workspace which had 3 GB file. But I wasn't able to refresh the the 250 MB dataset. Even dataset with 15 MB wasn't able to refresh. I was getting the following error:
I am confused because A1 has 3 GB RAM and it should be able to refresh the 250 MB dataset, but was unable to.
Is this an issue prevalent or there is something that I am missing on? Please guide.
Thanks.
Solved! Go to Solution.
Hi @rajulshah ,
According to error message and your description, your dataset can refreshed in general workspace and it will been blocked in premium workspace. I think it means that refresh requests amount are over the limit of current license.
Regards,
Xiaoxin Sheng
HI @rajulshah ,
I think this issue should related to your license Model Refresh Parallelism property.(A4 has 6 threads but A1 only has one)
Current it already handle other queries refresh and not have enough resource to handle your query.
Capacity Nodes | Total v-cores | Backend v-cores | RAM (GB) | Frontend v-cores | DirectQuery/Live Connection (per sec) | Model Refresh Parallelism |
---|---|---|---|---|---|---|
EM1/A1 | 1 | 0.5 | 2.5 | 0.5 | 3.75 | 1 |
EM2/A2 | 2 | 1 | 5 | 1 | 7.5 | 2 |
EM3/A3 | 4 | 2 | 10 | 2 | 15 | 3 |
P1/A4 | 8 | 4 | 25 | 4 | 30 | 6 |
P2/A5 | 16 | 8 | 50 | 8 | 60 | 12 |
P3/A6 | 32 | 16 | 100 | 16 | 120 | 24 |
Regards,
Xiaoxin Sheng
Hi @rajulshah ,
According to error message and your description, your dataset can refreshed in general workspace and it will been blocked in premium workspace. I think it means that refresh requests amount are over the limit of current license.
Regards,
Xiaoxin Sheng
Thanks for the response @v-shex-msft 🙂
Can this be the only reason? Because, I can easily refresh the same dataset in another workspace which is NOT backed by any capacity.
User | Count |
---|---|
24 | |
21 | |
11 | |
11 | |
10 |
User | Count |
---|---|
50 | |
31 | |
20 | |
18 | |
15 |