February 18, 2008 at 6:23 am
I am experience some problems with roll backs locking out users. This is why.
We basically have a table which records weather a record is locked and by what user. Every few minutes a job runs which checks the users in the table and then sees if there is anything in sysprocesses relating to that user. If not then it clears those locks from the table presuming the user has abnormally disconnected.
This works fine for most crashes but occasional the SPID relating to a user on an abnormal disconnection tries to Roll back and then sleeps. The actual roll back is very small but it can sleep for much more than an hour. Which results in that record being locked.
I can not see away around this , any ideas how to stop the roll back sleeping?
February 18, 2008 at 9:34 am
If I understand this, there's a SPID that's in rollback stage and you can't clear it?
Or is there something else?
February 19, 2008 at 3:55 am
This sometimes happens. The KILL command in SQL Server 2000 should have been called 'ShoutVERYLoudAndHopeYouScareItAway'.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply