Posted by Erland Sommarskog on 09/09/05 00:37

Holyman (jax@oncable.dk) writes:
> The applications on all the other machines
> deadlocket because they waited for the first application to commit.

No, they did not.

Terminology time: a deadlock occurs when two processes are waiting
on each other to release a resource that is locked by the other process.
This condition is detected by SQL Server, and SQL Server will select one
of the processes as a deadlock victim, and rollback that transaction.

If the application was waiting for the run-away transaction to committed
they were simply blocked, but that is not a deadlock situation.



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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Next in forum: Re: inner joins
• Prev in forum: Re: Re: Inserting large amounts of data
• Thread view: Re: Problem with uncommited transactions in log-file

[Reply to this message]