Forum Discussion
Refresh Now in Power Bi service
Hi,muhssamy I am glad to help you.
According to your description, you could use TE3 to refresh the whole model, there is a question, when the semantic model is changed to a large semantic model, according to the settings, power BI will automatically set the default segment size to 8 million rows, but you find that sometimes it is still 1 million rows of the small semantic model.
In real time, theoretically, when the large semantic model has been set to be enabled, the relevant configuration information will not be changed again (consistently maintaining the 8 million rows of data), which is rather strange.
It is possible that the large semantic model is not compressed as expected after a refresh due to the lack of available capacity on the current service when performing a refresh (i.e., when you click refresh now again, compression fails).
You can view the actual data configuration by checking the following with the powershell command or by exporting the gateway logs with the power BI On-premises data gateway appliction.
You can also manage worksapce via XMLA end point Related information: Use SSMS to check the estimated semantic model size in the Model Properties window.
Here is the official documentation on the subject, which we hope will help you:
URL:
Large semantic models in Power BI Premium - Power BI | Microsoft Learn
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
can i know this "It is possible that the large semantic model is not compressed as expected after a refresh due to the lack of available capacity on the current service when performing a refresh " from log analytics ?
the change to small model compression happen after re-publish the model from power bi desktop and initiate refresh now.Hi,muhssamy .Thank you for your reply.
Unfortunately, I don't have any experience testing detecting large semantic models at the moment. Here are some of my suggestions
You could try recreating a new workspace with large semantic model selection turned on, and then uploading individual reports of different sizes to detect what kind of scenarios would cause compression to fail. Keep the small semantic model
I've searched the site and found some documentation on testing and managing workspaces that I hope could help you out.
URL:
Using Azure Log Analytics in Power BI - Power BI | Microsoft Learn
New ‘ExecutionMetrics’ event in Azure Log Analytics for Power BI Semantic Models | Microsoft Power BI Blog | Microsoft Power BI
Can you share how you are looking at the workspace that has been set up with the large semantic model feature when refreshed, and how you are detecting if it is compressing properly to a large semantic model after refreshing, rather than incorrectly remaining as a small semantic model?
This will help more users on the forum. Looking forward to your reply.I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
"Can you share how you are looking at the workspace that has been set up with the large semantic model feature when refreshed, and how you are detecting if it is compressing properly to a large semantic model after refreshing, rather than incorrectly remaining as a small semantic model?
This will help more users on the forum. Looking forward to your reply"for this :-
we have configured the model itself as large semantic model not all the models in fabric workspace.i am detecting the compression through the vertipaq analyzer in coulumn tabs. you can see the relation between # segments and # Rows
