<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 Administration
»
Update stats job failed.
Update stats job failed.
Rate Topic
Display Mode
Topic Options
Author
Message
davidwarner
davidwarner
Posted Tuesday, November 13, 2012 6:32 PM
Grasshopper
Group: General Forum Members
Last Login: Thursday, January 24, 2013 2:06 PM
Points: 19,
Visits: 72
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
Joie Andrew
Joie Andrew
Posted Wednesday, November 14, 2012 3:59 AM
Mr or Mrs. 500
Group: General Forum Members
Last Login: Monday, May 06, 2013 5:58 AM
Points: 535,
Visits: 1,010
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
GilaMonster
GilaMonster
Posted Wednesday, November 14, 2012 4:09 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 3:05 AM
Points: 37,675,
Visits: 29,927
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 »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
