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.
The report pulls data from a Lakehouse using direct query.I don't think that is possible - did you mean to say from the lakehouse's SQL endpoint? There are many stories here about latency and schema mismatches when lakehouse updates have to be synchronized to the SQL enpoint.
Have you considered using Direct Lake instead?
lbendlin, Yep, the direct query is to the SQL endpoint. I haven't played with direct lake at all yet. These reports pre-date the launch of direct lake for reports. I'll give that a shot and maybe it gets around whatever is happening under the hood in these lakehouses.