July 13, 2009 at 4:23 am
Sometimes, around 1p.m getting deadlock in the production DB servers.
I have enabled the traces: 1204,1205 and 1222, so that can get the details in the SQL Server Error Log.
After that what are the steps, I need to perform to sequentially detect and end the deadlock?
Can you please suggest...?
Also to identify the blocking,locking and deadlocking are there individual tables available to get the clear cut details...like the Disk I/O, taking more memory and so on..?
In 2005 we have DMVs\system tables...and probably those are going to be used in the future versions and no longer the DBCC commands will be used.
Regards
Sourav
Thanks.
July 13, 2009 at 10:23 am
I'm not exactly sure what your question is, but locks and blocks are expected in SQL Server, it's what allows data to be consistent.
As far as Deadlock troubleshooting you should read the blog posts listed here.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply