![]() I did some searching around, but option(maxdop 1) did not solve the problem. How much is "the past"? I noticed in sys.dm_os_waiting_tasks the session being blocked by itself multiple times with wait type CXPACKET. I found Jeroen Mostert's comment interesting. I am in no position to make recommendations, much less update the server though. However, in hopes to keep this useful and hopefully come up with an answer, here is some more things I investigated, some facts, and thoughts on comments:įirst, the sql server version is 2008. When it was created, the performance was OK. I abandoned further debugging because I noticed that an index I thought existed didn't. If I am not mistaken on my 2 points, is it ever possible to have a deadlock? Wouldn't the deadlock require all of the involved users of a resource to be doing write operations on them, which would create a cycle in the resource request graph? I understand a timeout error in a select, but cannot understand a deadlock.
0 Comments
Leave a Reply. |