Forum Discussion
Advocate ILakehouse tables still visible in SQL endpoint view - how do I remove them?
Hi nioj2S,
Kindly contact your tenant administrator or Fabric administrator for further assistance in resolving the issue.
If the issue persists, we sincerely recommend reaching out to the Microsoft Support Team through the link provided below. Submitting a support ticket will allow you to receive personalized insights related to your account and potential resolutions:
Microsoft Fabric Support and Status | Microsoft FabricIf you find our response helpful, kindly mark it as the accepted solution and provide kudos. This will assist other community members facing similar queries.
Thank you.
I was in touch with Microsoft Support and the issue was that the original dataflow had managed to create a schema in the lakehouse, which was a lakehouse that did not support schemas. The steps they came up with to resolve the issue was:
1 - Create a Lakehouse with schema support.
2 - Using a Fabric notebook:
2.1 - Create the FIRMA1 schema in the new Lakehouse.
2.2 - Create a table called bl_project in the new schema with only 1 column.
2.3 - Copy the contents of the folder into the Lakehouse with the orphan tables.
3 - Wait for metadata synchronization to occur and check whether the orphan table returns the expected test column.
4 - Using a Fabric notebook:
4.1 - In the Lakehouse with the orphan tables, delete the bl_project folder.
5 - After metadata synchronization, check whether the bl_project table was removed.
6 - Repeat this process for all orphan tables.
7 - At the end, delete the FIRMA1 schema from the SQL endpoint.
Also, there was some issue with casing, so we had to use a piece of code to make sure that Spark ignored/didn't ignore capital ("BL_PROJECT" vs "bl_project").
This solved the issue. 🙂
Community SupportHi nioj2S,
Being a Workspace Admin in Fabric does not automatically confer permissions to drop tables or schemas in the SQL Analytics endpoint.
To drop a table or schema, you must have CONTROL permissions on the table, schema, and database or be a member of the DB_OWNER role.
If the necessary permissions are not granted, a SQL administrator must explicitly assign them using the SQL GRANT CONTROL command or by adding the user to the DB_OWNER role. SQL Server permissions, including ALTER, DELETE, and CONTROL, are essential for modifying database objects.
If you continue to face restrictions despite these measures, kindly reach out to your tenant administrator or Fabric administrator for further assistance.
If you find our response helpful, please mark it as the accepted solution and provide kudos. Your feedback will assist other community members encountering similar queries.
Thank you.
- nioj2S
Couldn't find anything clear in the Azure admin portal, so I accessed the lakehouse via Azure Data Studio, gave myself access to delete but still nothing. I have permission_name "ALTER", "CONTROL", "DELETE" etc. and when I run "CROP TABLE [FIRMA1].[BL_PROJECT]" I get the same error message, it does not exist or I don't have permission.