May 9, 2012 at 2:20 am
Recently i have upgrade my SQL server from 32bit to 64 bit(OS Win 2003 64bit/SQL 2005 64 bit) . After upgradation i noticed continous deadlock on one table. Can any one help to resolve this issue
May 10, 2012 at 2:44 pm
was there a change in the number of CPUs ? did you go from single/dual core CPUs to dual/quad/octo cores ?
I ask because paralellism may be a culprit ...
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
May 12, 2012 at 3:08 am
Hi Rudy,
I have upgrade from 4 CPU quad core to 4 CPU hexa core. I have set the max degree of Parallelism value=0.
Pl suggest whats needs to be done for this configuaration.
May 15, 2012 at 3:20 pm
Locking/blocking and deadlocks are more application code and database design related.
I asked about the upgrade in HW because it seems that that was the last thing to change - I have seen these issues escalate when newer and faster HW is put into play.
There is no quick fix ... however here are a couple of things to implement first that may put you on the path to find a solution for your issue ...
- implement deadlock trace flags 3605 & 1204 (or 1222 for XML)
- try changing MAXDOP to either 4 or 8 and see what happens
- examine your deadlock information
- is if between separate unique spids ?
- is it between parallel threads of the same spid ?
- you could even try MAXDOP=1 and force everything to be single thread
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply