Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now

Reply
SaravananM
Frequent Visitor

PowerBI data refresh failures

I got the below error message for all the reports which I have scheduled in PowerBI service.. Till last week everything goes fine with the same set of dataset. Kindly help me to get it resolve..

 

Data source error:The operation was throttled by Power BI Premium because there were too many datasets being processed concurrently. Please try again later.
1 ACCEPTED SOLUTION
v-zhangti
Community Support
Community Support

Hi, @SaravananM 

 

The error reported for you is that the advanced capacity needs to be optimized. You can try to optimize the model.

 

Consider the optimization possibilities for a DirectQuery model. 

At the datasource layer:

  • The datasource can be optimized to ensure the fastest possible querying by pre-integrating data (which is not possible at the model layer), applying appropriate indexes, defining table partitions, materializing summarized data (with indexed views), and minimizing the amount of calculation. The best experience is achieved when pass-through queries need only filter and perform inner joins between indexed tables or views.
  • Ensure that gateways have enough resources, preferably on dedicated machines, with sufficient network bandwidth and in close proximity to the datasource.

At the model layer:

  • Power Query query designs should preferably apply no transformations - otherwise attempt to keep transformations to an absolute minimum.
  • Model query performance can be improved by configuring single direction relationships unless there is a compelling reason to allow bi-directional filtering. Also, model relationships should be configured to assume referential integrity is enforced (when this is the case) and will result in datasource queries using more efficient inner joins (instead of outer joins).
  • Avoid creating Power Query query custom columns or model calculated column - materialize these in the datasource, when possible.
  • There may be opportunity to tune DAX expressions for measures and RLS rules, perhaps rewriting logic to avoid expensive formulas.

The size of a Premium capacity determines its available memory and processor resources and limits imposed on the capacity. The number of Premium capacities is also a consideration, as creating multiple Premium capacities can help isolate workloads from each other.

 

For more information on optimization, please refer to this document. https://docs.microsoft.com/power-bi/admin/service-premium-capacity-optimize 

 

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

6 REPLIES 6
v-zhangti
Community Support
Community Support

Hi, @SaravananM 

 

Has your problem been solved, if so, please consider Accept a correct reply as the solution or share your own solution to help others find it.

 

Best Regards

v-zhangti
Community Support
Community Support

Hi, @SaravananM 

 

The error reported for you is that the advanced capacity needs to be optimized. You can try to optimize the model.

 

Consider the optimization possibilities for a DirectQuery model. 

At the datasource layer:

  • The datasource can be optimized to ensure the fastest possible querying by pre-integrating data (which is not possible at the model layer), applying appropriate indexes, defining table partitions, materializing summarized data (with indexed views), and minimizing the amount of calculation. The best experience is achieved when pass-through queries need only filter and perform inner joins between indexed tables or views.
  • Ensure that gateways have enough resources, preferably on dedicated machines, with sufficient network bandwidth and in close proximity to the datasource.

At the model layer:

  • Power Query query designs should preferably apply no transformations - otherwise attempt to keep transformations to an absolute minimum.
  • Model query performance can be improved by configuring single direction relationships unless there is a compelling reason to allow bi-directional filtering. Also, model relationships should be configured to assume referential integrity is enforced (when this is the case) and will result in datasource queries using more efficient inner joins (instead of outer joins).
  • Avoid creating Power Query query custom columns or model calculated column - materialize these in the datasource, when possible.
  • There may be opportunity to tune DAX expressions for measures and RLS rules, perhaps rewriting logic to avoid expensive formulas.

The size of a Premium capacity determines its available memory and processor resources and limits imposed on the capacity. The number of Premium capacities is also a consideration, as creating multiple Premium capacities can help isolate workloads from each other.

 

For more information on optimization, please refer to this document. https://docs.microsoft.com/power-bi/admin/service-premium-capacity-optimize 

 

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

MikeJohnsonZA
Responsive Resident
Responsive Resident

Hi

 

This error does not mean that there is a problem with your report but rather the entire Premium capacity. More than likely someone has created a report(or reports) that is consuming all the resources.

 

To better understand what is going on you can use the Premium Metric App: Power BI Premium Metrics app - Power BI | Microsoft Docs

 

You will need the Power BI capacity administrator to set this up for you if you are not the administrator.

 

Regards

Michael Johnson

If this or other posts helped you, please consider giving it a thumbs up or even marking this as the solution.

Thanks Michael, I have the Premium Metrics App now and the Query waits showing as Unhealthy..

 

Also How to change the date time stamp in the metris App.. Now its shows the current date as FEB 11 in all the metrics App reports.

Hi Michael, Also I need to know how to kill those long running session in PowerBI service.

Capacity management can be tricky and there is usually not a single process that you can kill that will relieve all the pressure, perhaps there is simply too many reports and datasets running at the same time in which case you may need to look at increasing the size of the capacity. You will want to reduce the amount of memory used by optimising and consolidating data sets, and reduce CPU usage by refreshing data less often, improving DAX queries and limiting concurrent sessions(if possible), but again no silver bullet.

Microsoft does have some guidance on how to sort this out. Microsoft Power BI Premium capacity scenarios - Power BI | Microsoft Docs

 

#I can't think of why your data would be wrong, this does not seem right.

 

 

 

Helpful resources

Announcements
April Power BI Update Carousel

Power BI Monthly Update - April 2026

Check out the April 2026 Power BI update to learn about new features.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

FabCon and SQLCon Highlights Carousel

FabCon & SQLCon Highlights

Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.