Posted by Erland Sommarskog on 10/01/27 11:39

(dj) writes:
> I have a problem. When my computer loses connection to
> server during transaction it is rolled back automaticly
> by server after 2-5 minutes. During the time a can reset
> my computer, run my program again and I can see
> data from not commited transaction becouse I have to
> set isolation level to read uncommited.
> How to force the server immediately rollback transaction?

Apparently SQL Server does not sense that the client is gone. I will have
to admit that I don't know how that works. I would sort of expect that
if you pull the plug, SQL Server would be notified directly, but net-
working is not my best subject.

Anyway, if you can do sp_who and identify your process, you can use the
KILL command to stop the process directly. You need sysadmin privileges
to use KILL.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]