Forum Discussion
Fabric warehouse does not properly synchronize changes to OneLake
Hi there,
my Fabric warehouse did not properly synchronize changes to OneLake.
My workspace name is "Data Analytics [QA]" and warehouse name is "wh_analytics".
First, I created table [temp_fabric_sync_fix] in [dbo] schema. Later, I decided that this table should be transfered to another schema, so I created new [delete_corrupted] schema.
And I executed: ALTER SCHEMA [delete_corrupted] TRANSFER OBJECT :: dbo.temp_fabric_sync_fix;
The result is:
a) When looking via SSMS we can see the correct result, i.e. table [temp_fabric_sync_fix] is in the new schema - [delete_corrupted].[temp_fabric_sync_fix].
b) But, in OneLake we have folder "OneLake - Microsoft\Data Analytics [QA]\wh_analytics.Warehouse\Tables\delete_corrupted" and the folder [temp_fabric_sync_fix] is not here, but it still existis in [dbo] folder.
Of course, when I am trying to execute DROP TABLE dbo.temp_fabric_sync_fix I am getting: Cannot drop the table 'dbo.temp_fabric_sync_fix', because it does not exist or you do not have permission.
The operation was done a couple of days ago, and nothing has corrected since.
What's more interesting, I followed the same steps with other 2 tables, and the tableswere moved between schemas and OneLake folders properly.
My questions:
1. Why did it happen with temp_fabric_sync_fix? Is it a bug or did I something in a wrong way?
2. How to fix the problem with this bad-synchronized [temp_fabric_sync_fix] table?
Thanks in advance for you help.
HI RafalMonka,
Thanks for the update. Since the issue is still occurring, opening a Fabric Support ticket is the right next step to investigate and resolve the synchronization issue. Hopefully, the support team will help identify the root cause and provide a resolution.
Thank you.
4 Replies
Hi RafalMonka,
The ALTER SCHEMA ... TRANSFER appears to have completed successfully: the Warehouse metadata shows the new schema, while the OneLake folder is still out of sync. Since the table now belongs to the delete_corrupted schema, DROP TABLE dbo.temp_fabric_sync_fix is expected to fail. There is currently no documented way to force a Warehouse-to-OneLake metadata resynchronization for this case, and it is not yet listed in the Known Issues. Please confirm that the table is accessible under its new schema, then refresh the Fabric portal/OneLake Explorer. If the inconsistency continues, I’d suggest opening a Fabric Support ticket and including your workspace name, warehouse name, table name, the ALTER SCHEMA statement, and screenshots of both the SQL metadata and the OneLake folder structure so the backend synchronization can be investigated.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thank you.
Hi v-saisrao-msft,
Thank you for your information. I executed CREATE TABLE dbo.temp_fabric_sync_fix and it was successfully created. Then I inserted one dummy row (to force OneLake sync) and dropped the table again. Finally, it disappeared from OneLake. However, I repeated the steps with another table and it stuck in OneLake and despite multiple DROP, re-CREATE and DROP again the table is still in OneLake. Probably I will open a Fabric ticket as it seems that the sync mechanism is fallible.
HI RafalMonka,
Thanks for the update. Since the issue is still occurring, opening a Fabric Support ticket is the right next step to investigate and resolve the synchronization issue. Hopefully, the support team will help identify the root cause and provide a resolution.
Thank you.
Hello, I raised the issue with Microsoft Support Team, and it looks that OneLake File Exporer program is not displaying synced folders properly. Thanks for your support here.
