Forum Discussion
transient issue in directLake Semantic Model refresh
Hi stellahe102,
Here are the answers to your questions.
1. you can check recent changes by running the sys.delta_history function in a Fabric Notebook (Spark) or SQL query editor.
2. Could you turn off the refresh that is highlighted in the screenshot below
Regards,
Vinay Pabbu
Hi Anonymous 2 questions -
1. How/Where should I go to see if there is really a metadata update in the underlying delta tables? the pipeline generating the delta tables finishes a couple hours before the model refresh at 7am, so not sure why would the metadata still change at 7
2. there is only one scheduled refresh for the semantic model (see below), how should I stop the "additional" refresh?
Hi stellahe102,
Here are the answers to your questions.
1. you can check recent changes by running the sys.delta_history function in a Fabric Notebook (Spark) or SQL query editor.
2. Could you turn off the refresh that is highlighted in the screenshot below
Regards,
Vinay Pabbu
1. "sys.delta_history" is not working in fabric notebook, used "describe history table1" instead
2. Already turned off the directlake sync, seems no transient error any more, thanks for the suggestion!
Hi Anonymous I have an additional question - turning off the "Keep your directLake up to date" refresh button in the semantic model, will it affect the loading speed, or the CPU consumed when openning the dashboard built using this model?
Hi stellahe102,
Glad that your issue is resolved.
Turning off the "Keep your DirectLake up to date" refresh button in the semantic model will not affect the loading speed or CPU usage when opening a dashboard.
CPU usage during dashboard opening depends on query complexity, not the DirectLake refresh setting.If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Vinay Pabbu