Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hi,
So I'm having an issue with a data model that has a SQL server datasource and 8 excel files as data sources located on a network share that is accessible by the gateway. When I do a refresh on PBI desktop on my local PC it takes 5-10 minutes to refresh which was acceptable. However, I found that when I deployed it to the production workspace and did a refresh there it would take 90 minutes.
Has anyone run into similar issues before? I'm currently looking through the gateway logs but I thought I'd put the question out there.
Thanks
A ton of factors come into play:
You can start with performance tuning at Monitor and optimize on-premises data gateway performance | Microsoft Learn
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingSo there's another wrinkle with this issue. So I was getting errors refreshing the model on the service. Specifically I was getting a timeout issue on a specific table, I thought it was a related so I checked the model on PBI desktop to check if it would refresh there. I found that it also failed refreshing the table on desktop. But here's where it gets wierd, I grab the query for the table and run it on SMSS, works fine results return in like 2 seconds, 6200 rows. So same query on PBI desktop fails with timeout issue just like the refresh. If I adjust a table name in this case it's "pre_t" by adding another underscore to "pre__t" and it refreshes successfully with no issue. Is there any reason why making this change would even make a difference?
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
User | Count |
---|---|
52 | |
35 | |
32 | |
31 | |
25 |