Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
Anonymous
Not applicable

Schedule Refresh Failed

Hi, 

 

I have tried to schedule a refresh but it says failed to refresh and the following is shown as the failure details
"Failure details: Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. "

 

The scedule refresh is working for less number of data rows. When it comes to huge rows it gives this error message. 

Can I get any suggesstion for this error.

 

Thanks in advance

2 ACCEPTED SOLUTIONS
Pragati11
Super User
Super User

HI @Anonymous ,

 

You can enter something into timeout session area while you connect to your datasource in Power BI.

Something like below:

You can enter 120 for starting in the marked section below and check if it resolves the issue.

Pragati11_0-1628604669060.png

Thanks,

Pragati

 

Best Regards,

Pragati Jain


MVP logo


LinkedIn | Twitter | Blog YouTube 

Did I answer your question? Mark my post as a solution! This will help others on the forum!

Appreciate your Kudos!!

Proud to be a Super User!!

View solution in original post

v-luwang-msft
Community Support
Community Support

Hi @Anonymous ,

1. On the Power BI side, you could set timeout option and check again. The maximum is 2 hours.

vluwangmsft_0-1628735450295.png

 

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.

 

 

Best Regards

Lucien

View solution in original post

2 REPLIES 2
v-luwang-msft
Community Support
Community Support

Hi @Anonymous ,

1. On the Power BI side, you could set timeout option and check again. The maximum is 2 hours.

vluwangmsft_0-1628735450295.png

 

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.

 

 

Best Regards

Lucien

Pragati11
Super User
Super User

HI @Anonymous ,

 

You can enter something into timeout session area while you connect to your datasource in Power BI.

Something like below:

You can enter 120 for starting in the marked section below and check if it resolves the issue.

Pragati11_0-1628604669060.png

Thanks,

Pragati

 

Best Regards,

Pragati Jain


MVP logo


LinkedIn | Twitter | Blog YouTube 

Did I answer your question? Mark my post as a solution! This will help others on the forum!

Appreciate your Kudos!!

Proud to be a Super User!!

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.