SQL Analytics Endpoint unlinked from Lakehouse

[amaaiia]

Hi,

Few days ago I realized that the SQL Endpoint associated with a Lakehouse I have is not retreiving data. How can this be possible?

I check my Lakehouse and I have some tables (they're not new tables, I have data in this lakehouse for a few months ago):

Then, I check de associated SQL Endpoint, I refresh tables, and it's empty:

I've also tried to query the tables, just to check if it is an issue of visual interface, but it says "the table does not exist".

Any ideas?

[Anonymous]

Hi, @amaaiia 

Thanks for FabianSchut's reply. The documentation states that you can enable metadata synchronization if the table in SQL analytic Endpoint is not displayed, and you can try to display the table using this method

SQL analytics endpoint performance considerations - Microsoft Fabric | Microsoft Learn

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

How to get your questions answered quickly --  How to provide sample data in the Power BI Forum

[FabianSchut]

Can you refresh the SQL-endpoint manually and try again? The documentation for refreshing the SQL-endpoint can be found here: https://learn.microsoft.com/en-us/fabric/data-warehouse/sql-analytics-endpoint-performance.

"You can manually force a refresh of the automatic metadata scanning in the Fabric portal. On the page for the SQL analytics endpoint, select the Refresh button in the Explorer toolbar to refresh the schema. Go to Query your SQL analytics endpoint, and look for the refresh button, as shown in the following image."

[amaaiia]

Hi,

PowerBIEntityNotFound???

[FabianSchut]

Can you try to log out of your account and log back in? It seems some kind of authentication error.

[amaaiia]

I log out and log in every day, and I've been facing this issue (at least) for some days. However, I've already tried to log in with a different explorer, and the issue persists.

I've asked other users with access to the workspace to try it, and they have the same problem.