Unable to delete abandoned SQL endpoint from Fabric UAT workspace

[thefabricer]

We were trying to migrate fabric data from private workspace to dev workspace which is out UAT too.  We used ADO for migration. main branch is connected to UAT workspace. for one bronze lakehouse, there is an error indicating that the datamart and table are already in use, even though we are not using datamart in our process.

We discovered that there is a SQL endpoint in the workspace with the same name, which may be causing the issue due to the bronze Lakehouse name. We attempted to delete it, but it appears we don't have the necessary permissions even the lakehouse owner can't delete or rename it. We tried deleting it through PR, not working. The SQL endpoint is created for each lakehouse and each lakehouse has it's own datamart, This specific SQL endpoint might have created due to unfinished migration of lakehouse.

Is there any way we can remove this SQL endpoint?  We cannot rename our original lakehouse because it's dependencies on pipelines & notebooks in bronze and silver layer. Even the Owner of this SQL & Admin of workspace was not able to delete this. Please suggest some steps we can take here.

[v-venuppu]

Hi @thefabricer ,

May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.

Thank you.

[v-venuppu]

Hi @thefabricer ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @svenchio @spaceman127 for the prompt response.

I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.

Thank you.

[svenchio]

@thefabricer  just to understand the "issue" a bit better, you're talking about the SQL endpoint as an "independent" item from it's associated Lakehouse and as such, you are under the impression that It can be renamed without renaming the lakehouse it belongs to, and that is NOT how it works, we need to focus on the lakehouse it belongs, if you rename the lakehouse so it's SQL endpoint.

In other words, instead of focusing on the SQL endpoint, the root cause is the Lakehouse, AND THE LAKEHOUSE CAN BE EASILY RENAMED, via the portal or via API's, then then the next relevant question is, is there a reason why you can't rename the lakehouse? if you don't have access to its workspace due to permissions? Please let me know to assist with some alternatives to figure this out ... just for inspiration (and in case you find it useful) I had a similar case where I wanted to delete a workspace reference by a pipeline, but lacking permission to the pipeline ... so, I use the admin api to grant myself permission first,I know is not the exact issue you are fascing, but perhaps the idea of using the API could be useful  Removing Orphan Fabric Deployment Pipelines

If you share more detials, I may be able to help more  🤞 best of lucks 

[thefabricer]

Hi, The "issue" is that only sql endpoint is created in our UAT workspace not the lakehouse. so the lakehouse only not visible in workspace only sql endpoint is visible and we are not able to delete or rename it. We have tried with workspace admin access too but no luck. We will try using the API once, thank you for the reference issue.

[svenchio · Accepted solution]

Understood, let me suggest the following, without any guaranties as I just could not reproduce the issue, that is, having an orphan sql endpoint, seems like an edge case ... but i would like you to try the following , from the article I shared proviously, follow Step 1: Getting the Access Token and Step 2. Configure Postman Authorization,  assuming that you have the workspace where the endpoits is, have handy its Resource ID (image below show how to easily get this) 

7

Using postman,  get a list of SQL endpoint in your workspace replacing {workspaceId} with the Id of your workspace using GET over https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/sqlEndpoints (ref.  Items - List SQL Endpoints - REST API (SQLEndpoint) | Microsoft Learn ) 

Once you have the Id of the delinquent SQL endpoint, try to delete it replacing {workspaceId} with your workspace and {itemId}  with the Id of the SQL endpoint using DELETE over https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{itemId}  (Ref. Items - Delete Item - REST API (Core) | Microsoft Learn) 

Hopefully it works, but if not, I'm positive that you will receive more information as to why you cann't remove it!   ... give it a try and let me know! Best of lucks 

[spaceman127]

Hi @thefabricer ,

Hi,

Perhaps it's a problem with the GUI.

Have you tried using the Fabric CLI to see if you can display the resources or delete the lakehouse?

I've had very good experiences with it.

Here the GitHub Repo

https://github.com/microsoft/fabric-cli

Best regards