I am getting random deadlocking when Substitution rules are running within 1 table such as, "Transaction (Process ID 77) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction." The run then stops.
The most recent case was in table ClientEmployer. ID 09-0070 was updating PCode from dataset Postcodes +Prov +Town CND, while 09-0071 was updating Address from dataset Street Addresses.
Should I reduce to 1 Worker to avoid this?I dont' see any obvious dependency between these rules unless any operation within the same table should be dependent on previous ones completing. Please advise.
1 · Share on Twitter