June 17, 2011 at 1:34 am
[font="Verdana"]I am investigating a system in local test environment in which only 2 -3 users are connected with Database through application. And only one out of all connected users, got a deadlock message at application interface! But SQL Server Log logged more than 5 deadlocks in the system in same closed, short span of time.
Also to note that here is no exception handling in Application interface, and in case of any deadlocks the exact DB error message is displayed to users.
Furthermore a SELECT (Victim query in almost all cases; as per logged by SQL Event Log) query is consistently pinging Database after one second or so interval. And we have logged its error message too in text a file, as this particular SELECT query is somewhat called from a Service. After further analysis we got that only one deadlock was logged in that text file too, while SQL Server Error log contains more than 5 deadlocks as stated earlier.
and all deadlocks were on same DB (on which both Service and users were connected).
This all may be some understanding/ambiguous issue. But leads to one question
i.e
Do T-1222 has any reported known issues? or it may have reported Blocking too? 😎
Thanks for your valuable comments!!![/font]
June 17, 2011 at 1:39 am
I used to run a major production server with that traceflag permanently enabled. It can't cause blocking (thing to block)
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
June 17, 2011 at 1:42 am
GilaMonster (6/17/2011)
I used to run a major production server with that traceflag permanently enabled. It can't cause blocking (thing to block)
[font="Verdana"]Yes sure it doesn't cause blocking or in general performance overhead on Servers.
May question was that is this flag also logged details of blocking in Error Log? As we have witnessed one deadlock, but there were more than one deadlocks reported in LOG file!!!
Thank you![/font]
June 17, 2011 at 2:13 am
No, just deadlocks. If it reported blocking your error log would have more like 500 entries than 5.
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 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply