Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.

Reply
PavBidani
Helper II
Helper II

Performance issue - moving from import to direct query

Hello All,

Happy New Year!

Based on corporate guidance, we recently moved from import to direct query.

We are having performance issues - it is taking too long for data loads.

I will greatly appreciate any suggestions you may have - data model, dax, power bi setup, visuals, governance, etc.

Thanks very much,

Pav

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @PavBidani ,
Happy New Year to you as well! 
Here are some steps you can take to optimize performance:
1.Try to have a star schema design with one central fact table and several dimension tables. Avoid complex relationships and many-to-many relationships where possible.
2.Keep your DAX formulas simple and efficient. Complex calculations can slow down your report. If possible, apply filters directly in the source query to reduce the amount of data that needs to be processed.
3.You can also follow the official documentation process for troubleshooting
Troubleshoot report performance in Power BI - Power BI | Microsoft Learn
4.Another way to do this is use Performance Analyzer to examine report element performance in Power BI Desktop
Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Micr...

 

I recommend you start by reviewing the best practices for DirectQuery models which you can find on the official document
DirectQuery in Power BI - Power BI | Microsoft Learn

Best regards

Albert He

 

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

 

View solution in original post

2 REPLIES 2
Anonymous
Not applicable

Hi @PavBidani ,
Happy New Year to you as well! 
Here are some steps you can take to optimize performance:
1.Try to have a star schema design with one central fact table and several dimension tables. Avoid complex relationships and many-to-many relationships where possible.
2.Keep your DAX formulas simple and efficient. Complex calculations can slow down your report. If possible, apply filters directly in the source query to reduce the amount of data that needs to be processed.
3.You can also follow the official documentation process for troubleshooting
Troubleshoot report performance in Power BI - Power BI | Microsoft Learn
4.Another way to do this is use Performance Analyzer to examine report element performance in Power BI Desktop
Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Micr...

 

I recommend you start by reviewing the best practices for DirectQuery models which you can find on the official document
DirectQuery in Power BI - Power BI | Microsoft Learn

Best regards

Albert He

 

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

 

Thanks Albert.

Much appreciated!

Pavan

Helpful resources

Announcements
September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors