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.
The Lakehouse is a OneLake lakehouse and was created via Fabric Link. When I tried to run Optimize on a single table in the Lakehouse using Spark SQL it errored indicating that tables in the Dataverse cannot be maintained. My issue is that my client is trying to run a single query to drop a view and it ran for 5 minutes without completing. Since then performance has degraded for any query. When I inspected one of the highly transacted tables from D365 FnO that has been exported I could see that there were hundreds of 10MB files, I could see how this would cause performance issues. I want to optimize the table but this is failing either through the Fabric Maintenance operation or through a Notebook. I hope this provides clarity. Ultimately, I'm trying to optimize the client's experience with Fabric, as of right now they have an F8 sku and are seeing poor performance on querying and a high CU usage in the background for data coming from Fabric Link.
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.
Interesting, so then why do I see storage consumption in Fabric? When I look at the Fabric Capacity Metrics App I see consumption continuing to grow. The OneLake storage for this workspace is at 1.5 TB there needs to be some way to maintain this?
That is very odd, when you click on the table and view source files, what does it show you?