SQL-endpoint of Lakehouse completely broken after renaming

[NotebookEnjoyer]

Some time ago I renamed a lakehouse. Presumably since then, I'm not 100% sure (but I haven't done anything else either), the SQL endpoint is completely broken. The following symptoms occur:

• If I try to connect from an existing model/report from PBI desktop, it says my credentials are wrong. Same issue when I try to make a connection.
• If I connect a new, blank report to just the SQL enpoint connection string without specifying a database, it shows the old lakehouse name but this lakehouse does not contain any of my tables).
• If I run the SQL enpoint refresh surveillance script from here: Fix SQL Analytics Endpoint Sync Issues in Microsoft Fabric – Data Not Showing? Here's the Solution! ... , then it says the SQL sync state is "failure" for pretty much all tables that should have changed since the renaming of the lakehouse. Reads like this:
  "Table: gold_dimdate Last Update: 2025-04-16T16:03:14.0443295Z Table Sync State: Failure SQL Sync State: Failure"

First of all: Did I do something wrong? If not, this complete breakdown of functionality because of a rename is quite unacceptable. Then don't offer renaming if you can't swing it. Is there a way to get out of this without making a new lakehouse (again, had something similar already)?

Thanks for any help!

[v-prasare]

Hi,

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[v-prasare]

Hi @NotebookEnjoyer , 

if your blocked on this i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thanks,

Prashanth Are

MS Fabric Community support

[Ashim123]

Renaming a Lakehouse can break the SQL endpoint sync in Microsoft Fabric. Try republishing the Lakehouse or contact support to fix it.Hope it will help you.

[NotebookEnjoyer]

What do you mean by "republishing the lakehouse"?

[ucarbengisu · Accepted solution]

Renaming a Lakehouse should be safe, but in practice it often breaks the SQL Analytics Endpoint behind the scenes because the endpoint retains old internal mappings. Fabric currently does not fully resync metadata after a rename.

I experienced the same problem. After trying many different solutions without success, what finally worked was renaming the Lakehouse back to its original (old) name, and then renaming it again. This forced Fabric to rebuild the metadata and resolved the sync issues.

[NotebookEnjoyer]

While re-renaming the lakehouse apparently doesn't work (for me, for now), reverting to the old name at least let's me refresh my models and stuff. Good tip, thanks!