Race condition or bug in sql server using serializable TIL with updlock? - by dvdvorle

Status : 


Sign in
to vote
ID 836666 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 3/19/2014 4:43:31 AM
Access Restriction Public


Earlier I've posted the same question at stackoverflow which has better formatting, find it at http://stackoverflow.com/q/22361181/481635

I've been staring at this problem for almost a week now. I'm getting an unexpected deadlock in some query, and I've reduced the problem to these reproducible steps.
Sign in to post a comment.
Posted by Microsoft on 5/27/2014 at 4:33 PM
Closing this one.
If you do have repro scripts, feel free to file a new bug.

Posted by Microsoft on 5/9/2014 at 12:03 PM
Thanks for submitting this feedback.

I could not quite follow the repro, and the stackoverflow link seems to have been removed. Perhaps you could share the two scripts for the two sessions and number the steps for running the repro?
I am not surprised though that you are getting deadlocks when using several concurrent serializable transactions along with explicit locking hints.

What would be the use case of locking hints when using serializable? It is the highest isolation level, so you should be getting all the isolation you need.

Jos de Bruijn - SQL Server PM