Reply
avatar user
Anonymous
Not applicable

"Microsoft SQL: Execution Timeout Expired

lbsm_0-1572357539452.png

What will be the main reason for this issue?

1 ACCEPTED SOLUTION
v-eachen-msft
Community Support
Community Support

Hi @Anonymous ,

 

1. On the Power BI side, you could set timeout option and check again. The maximum is 2 hours.

3-1.PNG

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.

    

Community Support Team _ Eads
If this post helps, then please consider Accept it as the solution to help the other members find it.

View solution in original post

1 REPLY 1
v-eachen-msft
Community Support
Community Support

Hi @Anonymous ,

 

1. On the Power BI side, you could set timeout option and check again. The maximum is 2 hours.

3-1.PNG

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.

    

Community Support Team _ Eads
If this post helps, then please consider Accept it as the solution to help the other members find it.
avatar user

Helpful resources

Announcements
March PBI video - carousel

Power BI Monthly Update - March 2025

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

March2025 Carousel

Fabric Community Update - March 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors (Last Month)
Top Kudoed Authors (Last Month)