Forum Discussion
Error fetching data for this visual - Report with Direct Query to Lakehouse
Hey v-saisrao-msft, The product team doesn't consider it a bug but that this is how the SQL endpoint is supposed to work. So they consider the change they're working on as an improvement. It's not yet released to private preview but it is being worked on (so I'm told - I actually don't have proof).
The issue is that the SQL endpoint doesn't automatically refresh after some period of not being active. So for lakehouses that are accessed relatively infrequently - like daily - they need to be manually refreshed using the Refresh Metadata button on the SQL Endpoint for the lakehouse. Then it will automatically refresh for a little while but if it's not accessed again until (say) the next day, it'll shut off again.
My problem is the users access the report daily but don't have access to the lakehouse. They're not tech savvy enough. So I'm looking at the direct lake option or eliminating that lakehouse and pointing back to one that is accessed more frequently even if the data acess gets messy. Neither are great solutions.
Hi GregMarbais,
Thank you lbendlin, for your insights.
Make sure Lakehouse shortcuts are updated, rerun the necessary ingestion pipelines, and, if needed, use a metadata initialization query or Direct Lake to help minimize latency and schema mismatches. This will ensure reports are accessible without manual steps.
Troubleshoot healthcare data solutions - Microsoft Cloud for Healthcare | Microsoft Learn
Thank you.
v-saisrao-msft I'm not sure what you mean by updating the lakehouse shortcuts - I've definitely recreated them multiple times - at all points along the chain of lakehouses. The ingestion pipelines run regularly so they've definitely re-run many times since this behavior started. I'm pretty sure the issue is local to the workspace and lakehouse - the same tables showing the issue are working fine for other reports in other workspaces, pulling from other lakehouses.
I've never done a metadata initialization query so I'll have to look into that. And will look into Direct Lake as an option as well.
Hi GregMarbais,
Could you let me know if the issue has been resolved, and have you checked using the direct lake option?
Thank you.
v-saisrao-msft The issue hasn't been resolved but I've been told by the Tech Support team that the product team is working on a long-term fix. The issue has to do with how frequent the SQL endpoint refreshes metadata in lakehouses that aren't used often.
I have to change things around in the lakehouse and report before I can use direct lake so I'm going to try that but I'm not going to get a chance to do that for a bit.
Hi GregMarbais,
We haven’t heard back from you in a while regarding your issue. let us know if your issue has been resolved or if you still require support.
Thank you.