Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
In several of my different workspaces there are multiple StagingLakehouseForDataflows that I did not create. I understand it as the dataflows create them. But why are there so many? And how can I know which ones are even used? Right now they look like garbage, they take up room. Can I remove them?
One workspace:
Another workspace:
Thanks!
Solved! Go to Solution.
Hi @nioj2S ,
In Microsoft Fabric, StagingLakehouseForDataflows items are automatically created when you use Dataflow Gen2. These system generated lakehouses store intermediate data during refreshes, so you didn't create them manually. It's common to see several of them if you've created, changed, or deleted dataflows over time, as Fabric doesn't always remove unused staging lakehouses, which can lead to a buildup of extra items.
You can delete these lakehouses, but only after making sure they're not linked to any active Dataflow Gen2. To check, use the Lineage View in your workspace to see if any dataflows are connected, and review your Dataflows destination settings and recent refresh history. If they're not in use and haven't been refreshed in a while, they're probably safe to remove. As an extra step, you could rename the lakehouse and wait a few days, if no refresh fails, it's safe to delete it permanently.
Hi @nioj2S ,
In Microsoft Fabric, StagingLakehouseForDataflows items are automatically created when you use Dataflow Gen2. These system generated lakehouses store intermediate data during refreshes, so you didn't create them manually. It's common to see several of them if you've created, changed, or deleted dataflows over time, as Fabric doesn't always remove unused staging lakehouses, which can lead to a buildup of extra items.
You can delete these lakehouses, but only after making sure they're not linked to any active Dataflow Gen2. To check, use the Lineage View in your workspace to see if any dataflows are connected, and review your Dataflows destination settings and recent refresh history. If they're not in use and haven't been refreshed in a while, they're probably safe to remove. As an extra step, you could rename the lakehouse and wait a few days, if no refresh fails, it's safe to delete it permanently.
Great tip about looking at the Lineage view, looks like I can remove them. Thanks!
Hi @nioj2S ,
Thanks for the update
Glad the Lineage view helped you identify the unused staging lakehouses.
Hi @nioj2S ,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Hello @nioj2S
You are absolutely right. those StagingLakehouse for Dataflows entries are not ones you are manually created. They are automatically generated by Dataflow Gen2 in Microsoft Fabric asit's by deafult.
I would recommend you don;t delete those satging files, if you do that, your data flow will break. so pls check the staging dataflopw and if it shows recently refreshed or next refreshe scheduled don;t delete.
My strong advise is create Folders and move it to the folders section, so that it will easy to view th worksapce neat and clean.
Data in Dataflow Gen2 staging - Microsoft Fabric | Microsoft Learn
Hope this helps you!!
Thank you!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 14 | |
| 8 | |
| 7 | |
| 5 | |
| 3 |