The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have a power bi dataset, prior to this week (2023-08-28), that has been refreshing once a day on a schedule without issue. For some reason this week, as I have profiler open in ADS, I see that the queries complete that are a part of the data refresh. However, I look in power bi and the dataset is still showing refreshing. After about 5-10 minutes, I noticed that in profiler, the queries that are part of the data refresh kick off again. Not one time showing stopped in the Power BI server. It is like it just keeps going. The back-end queries have not changed nor the data. The service is not recognizing that everything has been completed. If that is not enough of a downer, when I connect to the dataset. It only holds the data from my desktop parameters. Even though incremental is turned on and I can see the stored procs being executed with the appropriate date ranges. I cannot think of anything else to try to see what the problem besides it could be being the service itself is hung. Any suggestions?
try republishing from your pbix to the workspace. If that doesn't help, remove the report and the dataset from the workspace and then re-publish (warning - this will create a new set of GUIDs!)
Is the workspace on Premium?
Thank you for the reply and suggestions. I have tried the suggestions multiple times to no avail. The workspace is Premium as well. However, it is not a Premium level where I can change capacity. I get confused on the subscription levels because we also have PBI Embeded. But, I do not think this workspace is tied to that. Thoughts?
Taking a workspace out of Premium and putting it back in will also stop all currently running refreshes and queries.
Yeah, I acknowledge this. But that is not my primary issue. The primary issue is that it continues to run even after the backend SQL finishes running. Then, internally, it kicks off a refresh again. I see the same SQL code getting executed after a period of time. The spinning wheel never stops spinning. There is no refresh turned on either.