Forum Discussion
Cannot Delete Lakehouse Issue
Update: If I first delete the one-time pipeline used to populate the Lakehouse, I'm able to delete the Lakehouse. It's like Fabric sees that something is connected to the Lakehouse and won't let me delete it. Is this expected behavior?
I tested again by creating a Lakehouse with a copy data pipeline, and a completely blank Lakehouse. The blank Lakehouse deleted with no problem. The other lakehouse would not delete until I deleted the associated pipeline first.
Do you have any other artifacts in that workspace? The automatically created staging lakehouse is shared by all lakehouses, warehouses, dataflows, and pipelines within the same workspace.
It is similar in concept to SQL Server's TempDB. Think of the workspace as a server and the staging lakehouse as its storage are for TempDB and swap files.
This isn't a perfect analogy as the staging lakehouse doesn't exactly work this way, but the point is you can't delete it until you delete everything that could potentially use it. And if you did delete it, the moment you add a new lakehouse, warehouse, etc., the staging lakehouse will automatically be recreated.
Hi, thanks for the answer. I understand the concept of it, just not sure, why it is acting the way it is.
We firstly created it in a workspace which already had active reports and data models in there, but previously was as PPU, not Trial for Fabric. Then switched the workspace to trial and added that one flow and deleted it, this was when this happened on the first time.
Then, also with another user we replicated this issue in "My workspace" which was completely empty. Creating the dataflow, exiting out of it, then deleting the flow, and still weren't able to delete the staging lakehouse. There was also a staging warehouse created which we were able to delete.
Here, it also shows only the lakehouse and all other tabs are empty.
Hi Anonymous ,
We have a bug filed, to delete the LH & WH upon deletion of the last.
Ideal workaround is to create a new Workspace as we cannot delete the stagging artifacts manually.
If in your case if that will not work, I request you create a support ticket so the team will be looking into this issue more closely.
Once you have a SR# , please do share that here, so that we can keep an eye on the same.
Hope it is helpful.Hi, thanks for the answer.
Unfurtunately, for us it wouldn't be an option to delete the workspace, we would have downtime for our PowerBI reports and this wouldn't be accepted. Right now, we created one "Test Flow" to somehow mitigated the 3 artificats that show up, if no other objects are created, it's the best of the worst of what I could come up with.
Where can I follow along this ticket, that would fix this? And would it be fixed also for users that have this issue or only those that will encounter this in the future?
Hi Anonymous ,
I suggest you create a support ticket so the team will be looking into this issue more closely.
Once you have a SR# , please do share that here, so that we can keep an eye on the same.Hi
Same problem here : cannot delete Lakehouse and cannot understand how to delete dependencies
How can I fix this issue ?
Thanks
