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
Hello.
What are some of the best practices when scheduling refreshes in power bi service?
I have several reports that need to be updated many times throughout the day. What happens is that some of the best refreshing times seem to happen after working hours. There are noticeable differences between the best and the worst refresh duration for each of these reports (might take 15 min or 1hour+ to refresh).
Does having the reports in different workspaces or schedule the refresh at different times better refresh performance?? Any thing I should try?
Thanks in advance.
Solved! Go to Solution.
Hi @filiparibeiro ,
The real cause of time is form the data source and if you are using certain types of gateways and if you are on "regular" license or Premium.
First, the data source - hitting refresh against the same data source in multiple reports simultaneously could cause slowness and one or more of the refreshes to fail. For example, SharePoint only allows so many connections at a time. If you are running multiple reports AND SharePoint is being used by lots of users at the same time, then you will encounter slowness. Other data sources are very slow and/or have strick connection limits which can cause refreshes to take a long time.
If you are using Gateways then the userid and user permissions and method of connection might affect the refresh times as well.
And, finally, a Premium license will tend to run faster (which is part of why you pay for premium) when data is refreshed.
There are lot of things that go into a refresh but, if your data is "daily" then I would suggest refreshing during the night (or off-hours) and then you are more likely to get acceptable refresh times.
Proud to be a Datanaut!
Private message me for consulting or training needs.
Hi @filiparibeiro ,
The real cause of time is form the data source and if you are using certain types of gateways and if you are on "regular" license or Premium.
First, the data source - hitting refresh against the same data source in multiple reports simultaneously could cause slowness and one or more of the refreshes to fail. For example, SharePoint only allows so many connections at a time. If you are running multiple reports AND SharePoint is being used by lots of users at the same time, then you will encounter slowness. Other data sources are very slow and/or have strick connection limits which can cause refreshes to take a long time.
If you are using Gateways then the userid and user permissions and method of connection might affect the refresh times as well.
And, finally, a Premium license will tend to run faster (which is part of why you pay for premium) when data is refreshed.
There are lot of things that go into a refresh but, if your data is "daily" then I would suggest refreshing during the night (or off-hours) and then you are more likely to get acceptable refresh times.
Proud to be a Datanaut!
Private message me for consulting or training needs.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.