Forum Discussion
Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the oper
Thanks for replies.
It is an azure sql database - on the clinet ssms it is 0 so runs permanently.
However, in power bi an incrementallly refreshed report timing out after 80 minutes.
Other reports we see tiemout afetr 5 hours in premium workspace thus don't understnad wheer ethe 80 minutes comes from - report itself has no timeout set so woudl have thought woudl eithre run for 10 minutes and timeout or 5 hours and timeout.
Given other reports and sqls can run over 10 minutes seems not to be a database timeout and just wondering if some setting somwhere for incremental refresh gest set to 80 minutes?
Howeverm in power bi
Did you consider my suggestion to modify the command timeout setting?
Yes - thanks for suggestion. Not done yet as we have many reports and ideally woudl have global timeout setting. Looking at the documenattion it suggests timeout of 10 minutes and we have other models which run for over 20 minutes successfully.
My understanidng is there is a default 30 second connection timeout and a 10 minute sql execution timeout as we have not changed any defaults and the model itself has no timeout specified in the M query thus not sure where the 80 minutes timeout coming from?
Any thoughts?
Also the report in service attempted to run 4 times - is this the defalut for on demand reports - attempts 4 times if fails first time?
Details
#
Type
Start
End
Duration
Status
Error
1
Data
18/08/2024, 10:08:42
18/08/2024, 11:28:56
01:20:14.326
Failed
2
Data
18/08/2024, 11:29:56
18/08/2024, 12:50:22
01:20:25.938
Failed
3
Data
18/08/2024, 12:52:22
18/08/2024, 14:12:49
01:20:26.600
Failed
4
Data
18/08/2024, 14:17:49
18/08/2024, 15:38:16
01:20:26.603
Failed
yes, the four attempts are the new standard and we are not happy about it. It greatly messes with capacity management.