Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Update stats job failed. Expand / Collapse
Author
Message
Posted Tuesday, November 13, 2012 6:32 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Sunday, December 8, 2013 10:48 PM
Points: 31, Visits: 124
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?
Post #1384362
Posted Wednesday, November 14, 2012 3:59 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Yesterday @ 7:28 AM
Points: 709, Visits: 1,417
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"
Post #1384527
Posted Wednesday, November 14, 2012 4:09 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 2:51 PM
Points: 42,756, Visits: 35,850
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 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1384528
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse