Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi
Using PBID June 2025.
I created Direct Query to Snowflake View.
It's very slow 470M rows.
I'll try moving the View to Dynamic Table. Other ideas to improve speed?
Thanks
W
Solved! Go to Solution.
Hi @UncleLewis
DirectQuery can be inherently slow, especially when working with large datasets like 470M rows – every interaction triggers a live query to the source. To improve performance, consider:
Minimizing complex DAX logic – keep calculations in Snowflake when possible.
Avoiding expensive functions like DISTINCTCOUNT, FILTER, and nested CALCULATEs in visuals.
Disabling Auto Date/Time hierarchy – it creates hidden tables and overhead.
Using aggregate tables – pre-aggregate data in Snowflake and expose summarized tables to Power BI.
Reducing visuals per page – each one sends its own query.
Testing with Import mode to check how much the model complexity affects performance (for comparison).
Trying to replace a view with a dynamic table might help only marginally unless the underlying logic is simplified.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
Hi @UncleLewis
DirectQuery can be inherently slow, especially when working with large datasets like 470M rows – every interaction triggers a live query to the source. To improve performance, consider:
Minimizing complex DAX logic – keep calculations in Snowflake when possible.
Avoiding expensive functions like DISTINCTCOUNT, FILTER, and nested CALCULATEs in visuals.
Disabling Auto Date/Time hierarchy – it creates hidden tables and overhead.
Using aggregate tables – pre-aggregate data in Snowflake and expose summarized tables to Power BI.
Reducing visuals per page – each one sends its own query.
Testing with Import mode to check how much the model complexity affects performance (for comparison).
Trying to replace a view with a dynamic table might help only marginally unless the underlying logic is simplified.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.
Hi @UncleLewis ,
Thanks for reaching out to the Microsoft fabric community forum.
I would also take a moment to thank @Ritaf1983 , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
Please go through the below solved issue which may help in solving the issue:
Solved: Direct Query is extremely slow - Microsoft Fabric Community
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Community Support Team
Hi @sergprim ,
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
Thank you.
Hi @UncleLewis ,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Thank you.
Hi @UncleLewis ,
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.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 97 | |
| 71 | |
| 50 | |
| 47 | |
| 44 |