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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
kobik
New Member

Microsoft SQL: Execution Timeout Expired.

Hi,
since we made a maintanance on our server (nothing was changed) we are incountering with this error
on average for the biggest cube the refresh time was 45 minutes...
what could possibly be the reason ?

 

1 ACCEPTED SOLUTION
jennratten
Super User
Super User

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

jennratten_0-1672072737994.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.

    

View solution in original post

1 REPLY 1
jennratten
Super User
Super User

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

jennratten_0-1672072737994.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.

    

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors