Data set refresh from SQL server taking a long time

[kdav]

Hi,

I publish and manage several Power BI reports across multiple workspaces all pulling from the same sources (SQL server), but only two reports in a particular workspace are having this issue.  It is taking from 1 1/2 to over 12 hours to refresh these two reports if they refresh at all.  They only take a minute or so to refresh via Power BI Desktop and have only taken a few minutes to refresh in the portal in the past.

I tried to re-publish these reports from Power BI Desktop to see if that would fix the issue but did not have success.  I do not get an error but the publishing never completes.  When I cancel publishing, I see an error that the "Object reference not set to an instance of an object."  When I try to publish these reports to a different workspace, it completes without issue and I am able to refresh the reports in the different workspace within a few minutes without any issue as well.  Unfortunately, I cannot delete the existing data sets/reports and re-publish them in the existing workspace because I need the URLs for the reports to stay the same.

Here's the screenshot of the refresh history for one of the reports:

Any thoughts on what might be causing these issues and what can be done to resolve them?

Thanks,
Kevin

[GilbertQ]

Hi there, just to confirm that when you publish the same report with the same data sources, using the same gateway to a different app workspace it refreshes really quickly?

Just trying to understand why.

[kdav]

Yes, that's correct.  When I publish the same report with the same data sources, using the same gateway to a different app workspace it refreshes really quickly.

[GilbertQ]

Ok, are there a lot of people accessing the reports and dashboards in the App Workspace that is taking a long time to refresh?

[kdav]

There are only these two reports in the workspace.  Each report has at most 30 views per day from less than 10 unique viewers.

[GilbertQ]

Ok thanks, I was trying to understand what was different. But it appears that nothing is different. The only suggestion is to log a support call with Microsoft.

[kdav]

Thank you!  I've submitted a request into Microsoft support for this issue.