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.
Thanks for the references! I'll do some more digging into the actual data, but yes, the inventrans table as an example is sitting at 3GB of delta lake files. I'm part of the D365 preview community groups on Yammer, so I may post my questions there and discuss with the Fabric Link product team.
Thanks for all your help as well!
I think the shortcuts can show with "xGB" (for example 3GB) in Fabric and the files can show in the "view files", but the data should actually be stored in Dataverse, if you are indeed using the Link to Fabric option.
But the shortcuts should not show as storage in the Fabric Capacity Metrics app (I think). Because the data should be stored in Dataverse, if using the Link to Fabric option.
Is there some other (non-shortcut) data in the workspace called Fabric? I.e. some data which is actually stored physically in that workspace.
I notice that your data storage in OneLake was first empty, and then there was some data from October 15, before it started increasing rapidly from October 24th. Is October 24th the day when you activated the link?
Or did some other process starting to generate data on October 24th, some process which physically stores data in OneLake, in the workspace called Fabric?
Best of luck in getting to the root of it! 😀
As mentioned by richbenmintz , OneLake File Explorer can perhaps provide some insights into this case.
Azure Storage Explorer is another option which provides a different view into the OneLake storage: Integrate OneLake with Azure Storage Explorer - Microsoft Fabric | Microsoft Learn