Forum Discussion
Bug Report - Changing Lakehouse name breaks SQL Endpoint
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.
- Anonymous2 years agoNot applicable
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.
- Anonymous2 years agoNot applicable
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?- Anonymous2 years agoNot applicable
Hi agneum ,
We haven’t heard from you on the last response and was just checking back to see if your query got resolved? Otherwise, will respond back with the more details and we will try to help.
Thank you