Persistent Table Issue in SQL Endpoint After Deletion from Lakehouse

[tegrus-coutinho]

I am facing the following issue:
I had a table that was encountering a loading error, so I deleted the table from the Lakehouse. However, when I enter the SQL Endpoint, the table continues to appear, even though it no longer exists in my lakehouse.
I am unable to delete it from there; I have tried various methods, but all have been unsuccessful. The drop table queries keep running for days and do not return any result. I am facing the same issue when trying to delete a view: significant slowness and no successful feedback.

[AndyDDC]

Hi @tegrus-coutinho you won't be able to delete a Table using the SQL Endpoint as that is read only when dealing with tables.  If you have deleted the table from the Lakehouse and can no longer see it in the Lakehouse (is this the case?) but you continue to see it in the SQL Endpoint then this may be a meta-data sync issue and you'll need to riase a ticket with MS.

With the dropping View issue, again this could point to some issue with the lakehouse/sql endpoint metadata process if you can't drop a view - again, raise with MS.

Can you also check if there are any open transactions by querying the SQL Endpoint:

select * from sys.dm_exec_sessions where open_transaction_count > 0

[tegrus-coutinho · Accepted solution]

@AndyDDC Thank you for your help.

After spending 2 days trying to run the deletes on the endpoint (with no success), it seems that Fabric automatically synchronized, and when I opened my endpoint, it was updated.