Question

I have a table with a clustered primary key index on a uniqueidentifier column. I have a procedure that runs the following psuedo functions:

begin transaction read from table 1 insert into table 2 update table 1 with pointer to table 2 record commit transaction 

This all works fine until the same procedure is executed concurrently from elsewhere. Once this happens, one of the executions gets deadlocked and terminated every single time on the primary key.

Any idea what I can do to prevent this, short of simply saying ‘don’t run it concurrently’? The transactions are currently running in READ COMMITTED isolation level.

Answer 1

Look here:

http://msdn.microsoft.com/en-us/library/aa213026(SQL.80).aspx

and here:

http://msdn.microsoft.com/en-us/library/aa213039(SQL.80).aspx