April 6, 2009 at 9:42 am
Krishna Potlakayala (4/6/2009)
Dean Jones (4/6/2009)
Krishna Potlakayala (4/6/2009)
Dean Jones (4/6/2009)
wrote:How can this be doen with Delete and Updates, i thought it was mainly reads.
You cannot use lower isolation levels with Insert,update and delete they always need exclusive locks on the records.
I have given you general idea of how you can minimize dead locks. did you perfmon your deadlocks? SQL Server locks: number of deadlocks/sec?
How are you saying you have deadlocks? I man did you trace it?
Yes I traces it with flag 1222 and I am reading the graph to try and trace what's actually happening etc.
Also, I have read that one can use TRY/CATCH to do retries in order to solve deadlocking problems.
See: http://msdn.microsoft.com/en-us/library/aa175791(SQL.80).aspx
Has anyone ever done this before in a production enviroment ?
April 6, 2009 at 10:14 am
Dean Jones (4/6/2009)
Also, I have read that one can use TRY/CATCH to do retries in order to solve deadlocking problems.
It won't solve the deadlock. It will just allow your code to catch the error thrown when the process becomes the deadlock victim.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply