Diagnosing Transaction Enqueue (TX) Locking Issue
From: Tim Callaghan <tcallahan_at_crunchtime.com>
Date: Thu, 11 Sep 2003 15:53:21 -0400
Message-ID: <06k1mv4pj39g8992j15k36q10tfpg6h5hn_at_4ax.com>
We have an inhouse replication process which is causing us headaches when we try to run more than one copy of it against the same target database (we support unlimited remote databases so we may have to process in 20 replication files on a Monday morning).
Date: Thu, 11 Sep 2003 15:53:21 -0400
Message-ID: <06k1mv4pj39g8992j15k36q10tfpg6h5hn_at_4ax.com>
We have an inhouse replication process which is causing us headaches when we try to run more than one copy of it against the same target database (we support unlimited remote databases so we may have to process in 20 replication files on a Monday morning).
The issue I'm seeing is that computer 1 starts processing in the inserts/updates and continues through the process.
Computer 2 starts processing inserts/updates fine as well but at some point gets blocked by computer 1.
The lock is a TX lock and I'm trying to understand what could cause it.
Any help would be appreciated.
Tim Callaghan
Received on Thu Sep 11 2003 - 21:53:21 CEST