Solved: Re: "Microsoft SQL: Execution Timeout Expired

Anonymous · ‎10-29-2019

What will be the main reason for this issue?

v-eachen-msft · ‎10-29-2019

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.

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

v-eachen-msft · ‎10-29-2019

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.

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

"Microsoft SQL: Execution Timeout Expired