The code you have given could cause deadlock. Even if the stored procedure purely consisted of the following statement deadlock could occur.
The code you have given could cause deadlock. Even if the stored procedure purely consisted of the following statement deadlock could occur. DELETE FooTable WHERE Param1 = @Param1 Depending upon the exact table definition and indexes available (which you have left out of your question).
– George2 Jun 4 '10 at 16:11 1 Well the way I was thinking was suppose that invocation 1 of the stored procedure ends up getting page locks on pages x,y,z but needs page a. Invocation 2 of the stored procedure ends up getting page locks on pages a,b,c but needs page x then deadlock would ensue. – Martin Smith Jun 4 '10 at 16:14 1 @George2 We have no idea how many pages will be affected by it as you haven't told us!
– Martin Smith Jun 4 '10 at 16:23 1 I am most definitely not a deadlock guru! Check out Remus Rusanu's posts for that stackoverflow. Com/search?
Q=user%3A105929+deadlock – Martin Smith Jun 4 '10 at 16:35 1 single delete statement or single delete record? If the latter then I can't construct a scenario either where it would happen. If the former then the earlier example I gave would do it (maybe relying on a parallel execution plan just to ensure that the locks weren't issued in a linear order).
– Martin Smith Jun 4 '10 at 16:52.
The only reliable way to answer your question is to run your own stress tests.
Sorry Alex, the question is not very clear. Please discuss here, which I had a more clearer description. Stackoverflow.Com/questions/2981121/… – George2 Jun 5 '10 at 16:31.
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.