Forum Discussion
Bug Report - Changing Lakehouse name breaks SQL Endpoint
If I rename the Lakehouse my SQL endpoint can no longer query any tables. If I click the Lakehouse in the Fabric experience I can preview data, but when I switch to SQL endpoint or connect to SSMS and attempt to query the table I get this:
Statement ID: {ECECF593-E66F-407A-AF02-A9119DD9F45B} | Query hash: 0x3DF5D4E9DBA3F36F | Distributed request ID: {A284AF58-53E2-487E-B475-1216D7079509}
Msg 24596, Level 16, State 2, Line 2
Failed to complete the command because the underlying location does not exist. Underlying data description: table 'dbo.batchjob', file 'https://onelake.dfs.fabric.microsoft.com/*removed for privacy*/Tables/batchjob/PartitionId=2020/part-00010-6835a919-33cc-4325-a521-ef31671c51bd.c000.snappy.parquet'.
7 Replies
Hi agneum - Thanks for using Fabric Community,
As I understand you were unable to execute any query in SQL Endpoint while renaming Lakehouse.
I tried to repro your scenario, here are my findings:
Initial Lakehouse name : gchenna_lakehouse_3
Updated Lakehouse name: gchenna_lakehouse_3_New
I can find that name change being reflected in Lakehouse but not at SQL Endpoint.
Note: In order to run your query successfully, please check lakehouse name in your query - it should be the updated lakehouse name.
Sorry for the inconvience, I have reached the internal team for help on this. I will update you once I hear from them.
In meantime can you please confirm whether you are able run the query by following above information?
Hope this helps. Please let us know if you have any further queries.No that doesn't work because the underlying tables in the lakehouse are shortcuts to parquet files in azure storage. I cannot see the shortcut defintion and have no way to change it. The shortcuts should be handled by Microsoft and there is some misconfiguration by the Dynamics 365 FnO / Azure Synapse Link team when it comes to chaning the name of the Lakehouse. The references from the shortcuts are not updated properly when the database name is changed.
Hi agneum ,
Thanks for reporting this, let me check with the internal team for help on this.
I will update you once I hear from them.Appreciate your patience.
Hi agneum ,
Response from internal Team -
"SQL endpoint should continue working even after failed rename, as it's using different endpoint to access data. Was it working before the rename? Renaming LH should trigger SQL endpoint rename too. Can you try renaming LH again and see if SQL endpoint gets renamed. LH or SQL endpoint names shouldn't affect shortcut functionality. Today there is no possibility to change shortcut target, or name, but we're working on updates that will enable these features.
Also, please note, that SQL endpoint can only read delta tables. If it's parquet tables then it won't be visible to SQL endpoint. What is SQL endpoint for a lakehouse? - Microsoft Fabric | Microsoft Learn "
Can you please do try with above information and share the output with us?
Are there any updates about this issue?
Because I'm facing the same problem and I discovered as well that the lakehouse is accessable via Fabrik Frontend (1), but not via SQL Endpoint (2).
There error mentioned that "the underlaying location does not exists", but when I check the displayed filename (3) I discover that the filename in the mentioned directory is different (4).
I assume that the file in the directory is the newest anf correct one und the one which is refered to is the old one.
As already ask be the other peoples in the history, "how and where is this info stored and how will it be updated"?!
Many thanks ans best regards
