March 26, 2013 at 7:43 am
Hi.
I have just captured deadlock info into the error log using trace flag 1222. Can anybody help me disecting the results as it looks like a mine field of info !!!!
🙂
March 26, 2013 at 3:44 pm
I think there is a problem in usp_CALLMAN_UPDATE_ADVISERS first look at this query execution plan and if it need any index. And
it is a query like this
Maybe you can use with(nolock) hint in this select and then update and check index fragmentation
AND ASD.[Status] IN (2<c/>4);
03/26/2013 12:20:01,spid23s,Unknown,AND ASD.DateTo > @CurrentDate
03/26/2013 12:20:01,spid23s,Unknown,WHEREASD.DateFrom < @CurrentDate
03/26/2013 12:20:01,spid23s,Unknown,ASD.AdviserID = ADV.AdviserID
03/26/2013 12:20:01,spid23s,Unknown,INNER JOINCallManager.dbo.CallMan_AdviserStatusDatesASDON
03/26/2013 12:20:01,spid23s,Unknown,FROMCallManager.dbo.AdvisersAvailabilityADV
03/26/2013 12:20:01,spid23s,Unknown,SETADV.[Status] = ASD.[Status]
03/26/2013 12:20:01,spid23s,Unknown,UPDATEADV
March 27, 2013 at 4:44 am
Thanks very much for your input.
I have taken a look at that sp and notice that the isolation level is set to Serializable ! I also notcied this in the error log provided.
Would it be advisable to change it to Read Comiited ?
March 27, 2013 at 5:21 am
I can t say any think about that what is your app is need?
March 27, 2013 at 5:49 am
I dont think the updates that the SP handles are critical - I will need to speak with the developers about this i think. Thanks for your help.:-)
March 27, 2013 at 8:38 am
http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx
Note there are 2 additional parts to this blog series.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply