Forum Discussion
Table UPDATE statements on the same Warehouse table.
Hi Abdul_Ismail,
Thank you tayloramy, for your insights.
This issue happens because parallel UPDATE statements on the same table create write-write conflicts under snapshot isolation in Microsoft Fabric. To fix this, avoid updating rows in parallel and use a set-based method like staging with MERGE or batch updates to minimize concurrent transactions. If necessary, run the ForEach activity sequentially (batch count = 1) and include retry logic to manage transient conflicts.
Transactions in Fabric Data Warehouse - Microsoft Fabric | Microsoft Learn
Troubleshoot the Warehouse - Microsoft Fabric | Microsoft Learn
Thank you.
Super UserHi Abdul_Ismail,
Fabric warehouses use Intent Exclusive (IX) locks for update statements, so there is no nice way to run multiple updates on the same table at the same time.
My recommendation would be to use a staging pattern, stage all your new records in a staging table, and then run a merge statement to update the final warehouse table all in one go.