Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
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 have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.