November 13, 2012 at 6:32 pm
For the first time our update stats job failed, the job runs at 5am in the morning when no one should really be using the database.
It failed with SQL severity 13, SQL message ID 1205, This suggests a deadlock occured? Given nothing else should be running on the server at this time i am a bit confused at what could cause the deadlock? Can the update stats process deadlock it's self? The only thing that overlaps the update stats is a translog backup. This shouldn't cause a problem?
November 14, 2012 at 3:59 am
You can try enabling trace flag 1222 to capture the deadlock information. Then you can analyze the deadlock further to see what is causing it.
Detecting and Ending Deadlocks
Joie Andrew
"Since 1982"
November 14, 2012 at 4:09 am
Error 1205 is indeed the deadlock error message. Update stats should not be able to deadlock with itself, as the only locks it takes are schema stability locks, and those are compatible with each other.
No chance anyone could have had any schema modifications running at the time? That's about teh only thing that should block a stats update.
Since you're on SQL 2008, you can pull the deadlock graph out of the system health extended events session. Post it here and we'll take a look.
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 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply