What will be the main reason for this issue?
Hi @Anonymous ,
1. On the Power BI side, you could set timeout option and check again. The maximum is 2 hours.
2. On the SQL side, you could use SSMS to check if there is a lock on one or more tables.
If your data is large, you could create views to optimize data size.
It is recommended to update the Connection Timeout and Command Timeout parameters in the relational Target Connection.
Hi @Anonymous ,
1. On the Power BI side, you could set timeout option and check again. The maximum is 2 hours.
2. On the SQL side, you could use SSMS to check if there is a lock on one or more tables.
If your data is large, you could create views to optimize data size.
It is recommended to update the Connection Timeout and Command Timeout parameters in the relational Target Connection.
Helpful resources
Power BI Monthly Update - May 2026
Check out the May 2026 Power BI update to learn about new features.
Data Days 2026 coming soon!
Sign up to receive a private message when registration opens and key events begin.
New to Fabric Survey
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
Power BI DataViz World Championships - June 2026
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
