Direct Query Perfromance Issue

[vamshikrishna20]

Hi Everyone, 

I am working on Power BI Report which is having data from two sources oracle sql and dataflows. i developed this report in direct query . In the report, i want to compare count columns from two tables and return True/false for each row. Table visual is working fine when i bring all fields but when i add measure to write True/False, visual is breaking out with resources limit exceeded. 

Can someone suggest any alternatives 

[Ritaf1983 · Accepted solution]

Hi @vamshikrishna20 

It’s not entirely clear what exactly you are calculating or how your model is structured, but if the report is breaking due to resource limits in DirectQuery, it may be worth trying some alternatives:

• Push as much calculation logic as possible back into the source (Oracle or Dataflow), so Power BI receives pre-processed data.

• Use aggregation tables to reduce the data volume calculated at query time.

• Consider switching part of your model to Import or Hybrid (Dual storage mode).

• Create pre-calculated columns or database views instead of doing the comparison in a DAX measure.

• Explore composite models if you are combining multiple sources.

• See if the measure can be computed at a grouped level rather than at row level to lower query load.

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

[v-nmadadi-msft]

Hi @vamshikrishna20 ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the suggestions  provided by the community members for the issue worked. Please feel free to contact us if you have any further questions.

Thanks and regards

[v-nmadadi-msft]

Hi @vamshikrishna20 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @vamshikrishna20 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-nmadadi-msft · Accepted solution]

Hi @vamshikrishna20 ,
Thanks for reaching out to the Microsoft fabric community forum.

The visual has tried to query too much data for Power BI to complete the result with available resources. Try filtering the visual to reduce the amount of data in the result.

Source: Troubleshooting tile errors - Power BI | Microsoft Learn

 When you run a DAX query in Power BI it will always use a certain amount of memory inefficient DAX calculations can cause a query to try to grab a lot of memory. In Power BI Desktop these queries may run successfully but be slow, but the Power BI Service can’t just let a query use as many resources as it wants (if it did, it may affect the performance of other queries being run by other users) so there is a resource governor that will kill queries that are too resource hungry. In the case of the visual above the query behind it tried to use more than 1GB of memory and was killed by the resource governor.

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[Shahid12523]

Import mode for at least one source → faster local comparison.

Pre-aggregate counts in Oracle/Dataflow → compare ready values.

Use calculated column (if row-level needed) instead of measure.

Compare only at aggregated level, not per row.

Use composite model (mix DirectQuery + Import).

👉 Best: Precompute counts in dataflow/SQL, then compare in Power BI.

[Ritaf1983 · Accepted solution]

Hi @vamshikrishna20 

It’s not entirely clear what exactly you are calculating or how your model is structured, but if the report is breaking due to resource limits in DirectQuery, it may be worth trying some alternatives:

• Push as much calculation logic as possible back into the source (Oracle or Dataflow), so Power BI receives pre-processed data.

• Use aggregation tables to reduce the data volume calculated at query time.

• Consider switching part of your model to Import or Hybrid (Dual storage mode).

• Create pre-calculated columns or database views instead of doing the comparison in a DAX measure.

• Explore composite models if you are combining multiple sources.

• See if the measure can be computed at a grouped level rather than at row level to lower query load.

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