Forum Discussion
Maintenance on Lakehouse Tables
Hi rtolsma ,
I believe the issue is that the Dataverse data is not actually managed by Fabric, tables are pointers to your dataverse environment, the error while annoying is correct.
Yup makes sense that this is a short cut into an ADLS Gen 2 storage facility that the Fabric instance doesn't have access to. So impossible to maintain, but I didn't realize that shortcuts would cause you to also increase your OneLake storage...seems like I'm doing exactly what was told us was the benefit, no data duplication but it appears that I'm consuming Dataverse storage and OneLake storage as well.
I'm pretty sure external shortcuts don't consume OneLake storage.
Do you see any indications that it consumes OneLake storage?
Edit: Sorry, just became aware of your screenshot from the capacity metrics app.
That is very surprising.
Can there be some other delta tables in this workspace (not managed by Dataverse)?
E.g. are you running some notebooks, pipelines or dataflows which create a copy of some of the Dataverse tables inside Fabric?
All the tables are directly related to the Link to Fabric configuration. However, this data has only been exported since 7 days ago. Its quite possible that an optimize and vacuum job hasn't been run yet on Microsoft's underlying storage facility.