Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Update stats job failed.


Update stats job failed.

Author
Message
PretendDBA
PretendDBA
Valued Member
Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)Valued Member (74 reputation)

Group: General Forum Members
Points: 74 Visits: 491
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?
Joie Andrew
Joie Andrew
SSC Eights!
SSC Eights! (968 reputation)SSC Eights! (968 reputation)SSC Eights! (968 reputation)SSC Eights! (968 reputation)SSC Eights! (968 reputation)SSC Eights! (968 reputation)SSC Eights! (968 reputation)SSC Eights! (968 reputation)

Group: General Forum Members
Points: 968 Visits: 1899
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"
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47145 Visits: 44346
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

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


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search