Timeline for why a session becomes a head blocker
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 8, 2016 at 21:05 | history | edited | Hannah Vernon♦ |
edited tags
|
|
| Apr 11, 2014 at 17:52 | vote | accept | BobNoobGuy | ||
| Apr 4, 2014 at 23:05 | history | tweeted | twitter.com/#!/StackDBAs/status/452220331147927553 | ||
| Apr 4, 2014 at 19:17 | answer | added | Kenneth Fisher | timeline score: 4 | |
| Apr 4, 2014 at 19:01 | comment | added | Aaron Bertrand | More info on @@IDENTITY vs. SCOPE_IDENTITY() | |
| Apr 4, 2014 at 18:57 | comment | added | Aaron Bertrand | Could you go through your code and find anywhere you're using @@IDENTITY (and change it to use SCOPE_IDENTITY() instead)? Also see if this is executed inside of a transaction, since you should be able to pull this data outside of that context (and prevent any subsequent queries from continuing to hold locks on the resource that generated the identity value in the first place). | |
| Apr 4, 2014 at 18:52 | history | asked | BobNoobGuy | CC BY-SA 3.0 |