@ganes There are a number of techniques for this but will depend heavily on what you are doing. For example, you could create aggregation tables so that you are not hitting the source system as often. You could try DirectLake in Fabric. You could also apply query reduction. Have you turned on "assume referential integrity" for relationships? You could also consider using a composite model. Or, you could use some third-party like AtScale and solve it that way.
User-defined aggregations - Power BI | Microsoft Learn
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!: DAX For Humans
DAX is easy, CALCULATE makes DAX hard...
@ganes There are a number of techniques for this but will depend heavily on what you are doing. For example, you could create aggregation tables so that you are not hitting the source system as often. You could try DirectLake in Fabric. You could also apply query reduction. Have you turned on "assume referential integrity" for relationships? You could also consider using a composite model. Or, you could use some third-party like AtScale and solve it that way.
User-defined aggregations - Power BI | Microsoft Learn
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!: DAX For Humans
DAX is easy, CALCULATE makes DAX hard...
Helpful resources
Power BI Monthly Update - August 2025
Check out the August 2025 Power BI update to learn about new features.
Fabric Community Update - August 2025
Find out what's new and trending in the Fabric community.
