Forum Discussion
"Error: DataSource.Error: Microsoft SQL: Execution Timeout Expired" When Refreshing Data Flow
Hi All,
I am attempting to refresh a data flow in Power BI Service but getting the below error:
Error: DataSource.Error: Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Request ID: 62f50212-2ddb-3bfa-6a11-861a68020c5c Activity ID: 483c4322-fe07-4903-885f-64c7652f3c83
This error occurs on a large fact table. Is it possible to up this timeout period somewhere? Other forum posts I have seen have suggested how to do this in Desktop but not Service.
I found this about Azure databases
"As you noticed, connecting to Azure SQL DB is a little different from connecting to a Microsoft SQL Server. Generally for Azure, you connect to individual databases, not an entire server - so there's really no concept of configuring server timeout settings"
I think this means that you cant do anything about the timeout on the SQL DB side?
3 Replies
Hi Anonymous ,
In the Data Source Settings for the SQL Server database you can increase the timeout. (You can modify it in the Data Source Settings itself or if this is just one place you are using it, you can modify it in the M code in the Source line.)
I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
Interesting one. After some research, the table its self isnt going over the size limits. If you change it to a view and add this to Power BI instead it works fine.
Could there possibly be any issues with using tables with a Column Store Index on them?
I found this about Azure databases
"As you noticed, connecting to Azure SQL DB is a little different from connecting to a Microsoft SQL Server. Generally for Azure, you connect to individual databases, not an entire server - so there's really no concept of configuring server timeout settings"
I think this means that you cant do anything about the timeout on the SQL DB side?
