Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello Everyone,
I have written the query for the following pointers raising an issue that I'm am not able to resolve:
I have more than 7 crore records in the table (fetching data from a SQL query) using DirectQuery mode.
The initial DAX measures was not working, so I rewrote it with optimized logic.
Even after optimization, the card visual keeps loading continuously and shows an error — what should I do?
Could anyone please help in resolving the issue?
Solved! Go to Solution.
Hi @pranjalagarwal1 ,
Thanks for reaching out to the Microsoft fabric community forum.
Thanks for sharing the details, since you are working with ~7–8 crore rows in DirectQuery mode, the behavior you're seeing is often related not only to the DAX logic but also to the underlying source performance, query folding, and overall model design. Even though you optimized the DAX expression, DirectQuery pushes most work down to the SQL source, so it's important to validate that the query being generated is efficient and the source has appropriate indexing. I would recommend reviewing Microsoft's official DirectQuery guidance.
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
Optimization guide for Power BI - Power BI | Microsoft Learn
Best Regards,
Community Support Team
The initial DAX measures was not working, so I rewrote it with optimized logic.
How do you know it is optimized? Did you check the query plan and server timings with DAX Studio?
Hi @pranjalagarwal1 ,
Thanks for reaching out to the Microsoft fabric community forum.
Thanks for sharing the details, since you are working with ~7–8 crore rows in DirectQuery mode, the behavior you're seeing is often related not only to the DAX logic but also to the underlying source performance, query folding, and overall model design. Even though you optimized the DAX expression, DirectQuery pushes most work down to the SQL source, so it's important to validate that the query being generated is efficient and the source has appropriate indexing. I would recommend reviewing Microsoft's official DirectQuery guidance.
DirectQuery model guidance in Power BI Desktop - Power BI | Microsoft Learn
Optimization guide for Power BI - Power BI | Microsoft Learn
Best Regards,
Community Support Team
Hi @pranjalagarwal1 ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .
Best Regards,
Community Support Team
Hi @pranjalagarwal1 ,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .
Best Regards,
Community Support Team
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |