Forum Discussion
SQL Fabrics – the report doesn’t get the updated data from SQL Fabrics
Hi pagen and v-dineshya,
I had a similar issue and tried steps 1 and 2 (as v-dineshya suggested), but they didn’t help in my case.
I have a pipeline that loads the data from bronze to gold, and at the end there’s a refresh activity that’s supposed to update the semantic model.
As far as I know, the refresh activity performs an enhanced refresh, which doesn’t clear the cache but only updates the data.
With a scheduled refresh directly in the semantic model, or a manual refresh, both the cache is cleared and the data is updated. You can see this difference in the refresh history of the semantic model.
In Data Factory, the refresh only updates the data, whereas a scheduled refresh updates both the data and the query cache.
Technically, you’d probably need to trigger the query cache invalidation via a REST API call at the end of the pipeline — but for me, that feels too complicated for this problem.
My solution was to set up a scheduled refresh about 30 minutes after the pipeline finishes.
I’m not sure if there’s a better solution, but this was the only thing that worked for me.
Edited: Of course the refresh button in the report or app did not work either. 😉
Hi sven_h ,
I forgot to mention, the problem is from a scheduled refresh, and the refresh is scheduled 30 min after the DB update.
Hi pagen ,
Power BI Pro Workspace does not include the Query Caching setting, but Premium Per User (PPU) Workspace include the Query Caching setting, your semantic model is in a Pro workspace, you cannot disable Query Caching, which might be causing the delay in reflecting updated data from the SQL Fabric DB.
Please try below workarounds to fix the issue.
1. If possible, publish the semantic model to a PPU workspace where you can disable Query Caching.
2. Instead of querying via the SQL endpoint, use Direct Lake mode for faster and more consistent data access. This avoids caching issues and checks near real-time data availability.
3. Please try to increase the delay between the SQL DB update and the semantic model refresh. even though the DB update finishes quickly, the data might not be fully committed or indexed.
4. Before triggering the semantic model refresh, use a Fabric notebook or a small script to query the SQL endpoint and confirm that the data is updated.
5. If you are using Fabric pipelines, you can set up dependent activities so that the semantic model refresh only triggers after the SQL DB confirms the update.
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Hi pagen ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Regards,
Dinesh
