What are the challenges you face when working across database platforms? Take the survey

Deadlock when synchronizing

mkraleymkraley Posts: 6
When we are synchonizing two databases with a lot of changes, we will often see a deadlock error:

Transaction (Process ID 52) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

If we turn off the transaction option (check "Do not use transactions in synchronization scripts") then the deadlock doesn't happen. But we'd far prefer to run with transactions, just in case anything happens.

I find it hard to understand why running a simple (if long) DML script on a completely inactive database can be deadlocked. What could it be deadlocking with? I tried looking with the deadlock trace flags, but they don't seem to tell me about the other process.

Another clue is that this tends to happen a little over 30 secs into the sync process - seems like it might be a timeout. But it seems to happen the same place all the time.

what is causing this? and is there any workaround other than turning off transactions?


Sign In or Register to comment.