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

Get Fabric certified for FREE! Don't miss your chance! Learn more

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
Sticker Challenge 2026 Carousel

Join our Community Sticker Challenge 2026

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

January Power BI Update Carousel

Power BI Monthly Update - January 2026

Check out the January 2026 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.