|
Home > Archive > MS SQL Server > April 2006 > Why can I never kill blocks?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Why can I never kill blocks?
|
|
| Maury Markowitz 2006-04-06, 11:24 am |
| Periodically we get blocks in our DB. I don't really care, it happens rarely
enough that manual intervention is fine. However, the manual intervention
doesn't work.
I do what seems obvious: go into Enterprise Manager, find the blocking
process, and attempt to kill it. But nothing ever happens. It just sits
there, blocking, forever. The only solution is to restart the server.
Does anyone know why Kill doens't work? Before you say it might be doing an
expensive rollback or something like that, I will point out that every time
I've looked at it, the T-SQL is a trivial read-only query that normally
completes in a millisecond or so. There's nothing to rollback, commit, or
anything else.
Maury
| |
| MSLam 2006-04-06, 11:24 am |
| Maury,
What is the source of the read-only query? If it is a service running
behind, you will need to stop the service. Otherwise, it will keep
opening the connection regardless of how many times you kill it.
For example, one of my 3rd party application has a daemon running
against the db (when users submit jobs, the daemon then kick off
matching processes). I will need to stop the daemon/service before I
can restore the db.
Hope this helps.
Mel
|
|
|
|
|