Database Timeouts : Error -2 Severity 11

Question

Database Timeouts : Error -2 Severity 11

Query Shepherd

SSCrazy

Points: 2988
More actions
March 8, 2013 at 5:34 am

#269394

Hi Folks,
at times with heavy workload, my devs tell me they receive a lot of database timeouts. A the database I got 2 stored procs which get heavily executed. If I run the queries at ssms they take about 1000 ms. The execution plan looks good. But the cpu goes up to 100% and I got a lot of SOS_SCHEDULER_YIELDS. I've allready gone through all the points of chapter 3 in the book "the accidental dba", but none of the reasosn fit. Why is the query so ressource intensive?
Greetz
Query Shepherd

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Ant-Green SSC Guru Points: 113445 More actions · Answer 1

Can you disclose the procedures, tables, indexes, execution plans and any other information related to the objects in question so that we can take a look.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

Please post table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Also note that you need to tune your workload, not your individual queries.

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

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

Query Shepherd SSCrazy Points: 2988 More actions · Answer 3

Seems to be gone...weird...I'd come back with all the info, when the problem would emerge again. Thanks!

Greetz
Query Shepherd

colin.Leversuch-Roberts SSC Guru Points: 52643 More actions · Answer 4

running in SSMS isn't always the same as running from an application, the set options might be different for example.

if it's only a couple of procs why not profile to capture the stats when they run - you could also extract the plan from cache when it's bad and compare to the plan you get when you run it.

Sorry don't have the book so have no idea what all the steps there might be.

probably a silly question but the procs don't start sp_ ??

[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/