Cause of a process being a deadlock victim?

Q1: No. The SELECT is the victim because it had only read data, therefore the transaction has a lower cost associated with it so is chosen as the victim.

Here is how this particular deadlock problem actually occurred and how it was actually resolved. This is a fairly active database with 130K transactions occurring daily. The indices in the tables in this database were originally clustered.

The client requested us to make the indices nonclustered. As soon as we did, the deadlocking began. When we reestablished the indices as clustered, the deadlocking stopped.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.