Timeline for Managing concurrency when using SELECT-UPDATE pattern
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 8, 2021 at 8:36 | comment | added | George Menoutis | The 6 lines of this answer have proven more useful than many others I've read. | |
| Mar 22, 2012 at 21:29 | vote | accept | ErikE | ||
| Feb 13, 2012 at 16:45 | comment | added | Martin Smith |
@ErikE - The conversion deadlock in Alex's article is converting from IX to X on the heap itself. Interestingly no rows qualify so no row locks ever get taken out. Not sure why it takes the X lock at all.
|
|
| Feb 13, 2012 at 5:31 | comment | added | ErikE | Bizarre, @alex. I imagine it has to do with a race condition of the engine trying to find what to lock before actually UPDLOCKing it... | |
| Feb 13, 2012 at 2:05 | comment | added | A-K | +1 but: for heap tables you can still get a conversion deadlock even with update locks: sqlblog.com/blogs/alexander_kuznetsov/archive/2009/03/11/… | |
| Feb 12, 2012 at 13:40 | history | edited | Martin Smith | CC BY-SA 3.0 |
deleted 8 characters in body
|
| Feb 12, 2012 at 13:35 | history | answered | Martin Smith | CC BY-SA 3.0 |