May 22, 2018 at 11:20 am
Lynn Pettis - Tuesday, May 22, 2018 9:52 AMSue_H - Tuesday, May 22, 2018 8:52 AMLynn Pettis - Tuesday, May 22, 2018 8:20 AMJohn Mitchell-245523 - Tuesday, May 22, 2018 8:13 AMI can't open your file - just as likely to be due to restrictions this end as to anything wrong with the file itself. Combing through a deadlock graph isn't easy, though, which is why you might struggle to get someone to do it for you for free. Try going through this, and don't skip any steps. It may be a little tedious, but if it enables you to fix your deadlock, it'll be worth it.John
Same here. Can you try recreating your archive file, perhaps using 7zip instead? Just an idea.
I got it open with 7zip - had to unblock it first.
Sue
How? I was able to download it but can't open it.
I right clicked on the file, check properties, at the bottom of that window remove the checkbox, radio button whatever it was, to unblock.
Sue
May 22, 2018 at 12:27 pm
vsamantha35 - Tuesday, May 22, 2018 11:07 AMLynn Pettis - Tuesday, May 22, 2018 10:27 AMYou have all the information available to solve this problem, we don't. All you have provided to us is the deadlock graph. This is not enough to even try and help you. Without the queries, the table and index definitions all we can do is take shots in the dark while wearing a blind fold and hope we hit a target, any target.
Another way to put it, we can't see what you see.
I understand sir. Even I am facing the same problem. This is a deadlock which is generate by .NET Entity framework code first model which converts the .net code to sql and runs at the backend. The front end team wasnt co-operative. Even I have requested them if they can reproduce the issue using plain tsql in ssms but the dont respond... Thought collecting the deadlock graph can help.
How about using SNAPSHOT isolation level? If nothing works, not sure thinking to put a dirty fix.
You can get the deadlock information without the front end team. Deadlocks are a database thing so it's generated in SQL Server. You can get the information from the built in extended event session system_health. Check the following link:
Did you know , Dead locks can be track from the System Health in SQL 2012
You'd have the information for the sql statements involved, the tables involved, the indexes on those tables. No one else up here has that information. That's what is meant by you have the information, we don't. Check the queries involved and try to tune those.
Sue
May 22, 2018 at 12:55 pm
I cannot see object Common.Changesets mentioned anywhere in the query quoted in the XML.
Did you look out for triggers?
_____________
Code for TallyGenerator
May 22, 2018 at 8:55 pm
Sergiy - Tuesday, May 22, 2018 12:55 PMI cannot see object Common.Changesets mentioned anywhere in the query quoted in the XML.Did you look out for triggers?
Thats a good point. I will check on that. Thanks.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply