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.
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,
Hi, just checking back in — do you know if the product team’s fix has been rolled out to your tenant yet, and if things are working correctly now on your side?
Thank you.
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,
Checking in to see if your issue has been resolved. let us know if you still need any assistance.
Thank you.
v-saisrao-msft I tried the direct lake capability but had the same issue so I'm going to mark my post summarizing what Tech Support and the Product Group said as the solution - hopefully that will resolve it long-term.