You can cause a deadlock, but SQL Server detects deadlocks and chooses which process is rolled back.

If memory serves, in SQL2K, the victim is the one that will require the least work to roll back, although you can influence the decision SQL Server makes.

See Deadlocks in BOL.

P


-----Original Message-----
From: Edwin Uy
[mailto:mssqldba-ezmlmshield-x39128483.[Email address protected]
Sent: Monday, June 28, 2004 8:24 PM
To: LazyDBA Discussion
Subject: Simulating DEADLOCKS for Performance Tuning/Troubleshooting


Hi all,

I know, I've asked this before but unfortunately, my mail box got
cleanup/archive by accident. Am trying to check on performance
tuning/troubleshooting, can anyone tell me how to simulate a deadlock
which I will of course kill the other session that is causing it.

Cheers,


EDWIN ONG UY
\\|//
(o o)
^"^"^"^"^"^oOOo"^(_)^"oOOo^"^"^"^"^"^"^"^"^"^"^

"Choose a job you love, and you will never have to work a day in your
life." --Confucius
"How do I work? I grope." -- Albert Einstein
"Experience is the best teacher, enrolling in the class is the biggest
problem." -- Anonymous



---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]



MS Sql Server LazyDBA home page