![]() 14:25:54.66 spid4 -Ĭan you show us us the update that''s on line 88 of uspFacilitySchedulerUpdateAssign and the select that's on line 8 of uspFacilitySchedulerGetAssignBySchedule. One is a an update and the other is a simple select (there are no joins).The dead-lock graph is shown below. I set all the trace flags and ran sqldiag and the problem seems to be a particular index I have on a heavily used table.When I look at the deadlock graph it looks like I have one process that has an X lock on one part of the index and wants another X lock on another part of the index and a second process that has a S lock on the part of the index the 1st process needs and wants an S lock on the part of the index the 1st process has locked.The statements involved are pretty straightforward. The app I've been working on has been having a lot of deadlocks lately. Hey, I hope somebody smarter than me can help out with this. We've got lots of great SQL ServerĮxperts to answer whatever question you can come up with. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |