Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
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 ?
Solved! Go to Solution.
On the Power BI side, you could set the timeout option and check again. The maximum is 2 hours.
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.
On the Power BI side, you could set the timeout option and check again. The maximum is 2 hours.
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.
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 18 | |
| 7 | |
| 7 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 49 | |
| 45 | |
| 25 | |
| 25 | |
| 25 |