Forum Discussion

RafalMonka's avatar
RafalMonka
Icon for Helper I rankHelper I
3 months ago
Solved

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_fabr...
warehouse
  • v-saisrao-msft's avatar
    v-saisrao-msft
    3 months ago

    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.

v-saisrao-msft's avatar
v-saisrao-msft
Icon for Community Support rankCommunity Support
3 months ago

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.