Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

"Microsoft SQL: Execution Timeout Expired

What will be the main reason for this issue?
Need Help
  • v-eachen-msft's avatar
    v-eachen-msft
    6 years ago

    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.

        

v-eachen-msft's avatar
v-eachen-msft
Community Support
6 years ago

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.