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 moreJoin 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
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
Check out the April 2026 Power BI update to learn about new features.
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.
| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |