Forum Discussion

po's avatar
po
Post Prodigy
1 year ago

Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the oper

Hi ,

 

We have an azure sql database and using virtual neywork data gateway to refresh reports via the service and these work o.k.

 

However, one report seeing an issue with is incremnetal refresh one which looks to be consitently timing out after 80 minutes.

 

Is ther some setting which is controlling this - not set at power bi desktop level and in ssms doesn't appear to be set.

 

How can se wee where it is set and increase if necessary?

 

Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-

 

Thanks

 

6 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi, po 

    By default, SSMS waits forever for the query to complete. If you get this error, it's because a query timeout is set under Tools -> Options->Query Execution->SQL Server->General->Execution Timeouts. You can also change it for the current window by right-clicking and selecting "Query Options" from the bottom of the context menu. Set the timeout to 0 to wait permanently.

    In general, long-running queries are the root cause of timeouts. Try to optimize your queries to reduce execution time. You can use SQL Server's execution planning and performance tuning tools to identify bottlenecks. Make sure that Azure SQL Database has enough resources. You may need to scale up your database to a higher service tier to handle your workload more efficiently.
    You can also try using Azure SQL Database's monitoring tools to track query performance and identify any issues. You can use extended events or SQL traces to identify queries that are causing timeouts. You can check the following link:

    Troubleshoot query time-out errors - SQL Server | Microsoft Learn

     

    How to Get Your Question Answered Quickly

    Best Regards

    Yongkang Hua

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • po's avatar
      po
      Post Prodigy

      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 

      • lbendlin's avatar
        lbendlin
        Super User

        Did you consider my suggestion to modify the command timeout setting?