Error fetching data for this visual - Report with Direct Query to Lakehouse

Hey all, I'm hoping someone on here may be able to help me. I've already entered a ticket and been in a back and forth with them but getting nowhere 😞. On a daily basis, I have a few reports th...

one lake

workspaces

GregMarbais
9 months ago
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.

GregMarbais

Kudo Collector

10 months ago

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.