April 17, 2008 at 12:45 am
Hi
We are currently perf testing our application(sql 2005) with a load of 30 concurrent users and we are getting few deadlocks . I enabled the Trace 1204 flags to read the deadlock info from the error logs . Though i get useful info regarding some of the calling procs involved, type of operation, lock type,spid but i cant interpret what table and index is involved . I get soemthing like
04/16/2008 12:59:32,spid4s,Unknown,KEY: 9:72057594112638976 (1a002279bdd5) CleanCnt:2 Mode:X Flags: 0x0
So the problem is i am getting dbid:and then the 17 digit long number . In sql 2000 i used to get something like dbid:objectid:indid , making it easier to get the objectid or table involved . All reference material that i could find also points to the set of dbid:objectid:indid . So could someone please explain to me how to get the objectId/table and index from
KEY: 9:72057594112638976
Let me know if i need to send the full deadlock info for both the nodes.
April 17, 2008 at 1:41 am
I believe that's the partition_id.... Try this query in whatever DB has the ID 9
SELECT object_id, index_id from sys.partitions where partition_id = 72057594112638976
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
April 18, 2008 at 1:11 pm
Here is the bible on deadlock troubleshooting: http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx
Note that there are two continuations to that posting.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
April 21, 2008 at 1:45 pm
you really need other trace flags, depending upon what i want to do I use 1204,1205 and 1206. 1204 isn't sufficient to get all the data.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply