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 12345»»»

Running out of workers Expand / Collapse
Author
Message
Posted Thursday, August 8, 2013 6:50 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 11, 2014 11:23 AM
Points: 337, Visits: 598
Is there a way to set up a trace that will show why you are running out of workers?

I know that I will need to capture blocking, but is there a way to track the workers themselves?
Post #1482294
Posted Thursday, August 8, 2013 6:58 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: Today @ 3:35 AM
Points: 40,606, Visits: 37,059
What errors/messages suggest that you're running out of worker threads?

What version of SQL, what processor architecture, how many cores?



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 #1482301
Posted Thursday, August 8, 2013 8:02 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 11, 2014 11:23 AM
Points: 337, Visits: 598
Unable to log into the server and ...

SQL Server Alert System: 'Out of Workers' occurred on <Server Name>

DATE/TIME: 7/17/2013 8:53:43 AM

DESCRIPTION: New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 300 seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: 0%. System Idle: 95%.


COMMENT: (None)
Post #1482347
Posted Thursday, August 8, 2013 8:05 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 11, 2014 11:23 AM
Points: 337, Visits: 598
IT will not allow us to use the SA account, so there is no way.. that I know of .. to get into the server when it is effected. Once you can get in.. my blocking query shows no problems, and running a listing of workers shows just the normal stuff.
Post #1482348
Posted Thursday, August 8, 2013 8:22 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: Today @ 3:35 AM
Points: 40,606, Visits: 37,059
GilaMonster (8/8/2013)
What version of SQL, what processor architecture, how many cores?


The DAC connection requires a sysadmin, not necessarily SA, so you should be able to use that to connect.



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 #1482359
Posted Thursday, August 8, 2013 8:38 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 3:45 AM
Points: 5,480, Visits: 10,306
This video talks about exactly the problem you're having.

John
Post #1482369
Posted Thursday, August 8, 2013 3:54 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, December 12, 2014 1:02 AM
Points: 823, Visits: 753
If you run out of workers, this is likely to be due to one of the following (or a combination thereof):

1) There are simply too many active users.
2) There are too many parallel queries.
3) You have set "Max worker threads" to a low value.


Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Post #1482595
Posted Friday, August 9, 2013 7:11 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 11, 2014 11:23 AM
Points: 337, Visits: 598
GilaMonster (8/8/2013)
GilaMonster (8/8/2013)
What version of SQL, what processor architecture, how many cores?


The DAC connection requires a sysadmin, not necessarily SA, so you should be able to use that to connect.


When the Sql Server instance stops responding.. and I try to connect using Management Studio, it times out.

We are running 2008 R2 Standard, two CPU's with 6 cores each.
Post #1482757
Posted Friday, August 9, 2013 7:17 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 3:45 AM
Points: 5,480, Visits: 10,306
Did you follow the link I posted to watch the video? You need to use DAC.

John
Post #1482760
Posted Friday, August 9, 2013 7:20 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, December 11, 2014 11:23 AM
Points: 337, Visits: 598
Erland Sommarskog (8/8/2013)
If you run out of workers, this is likely to be due to one of the following (or a combination thereof):

1) There are simply too many active users.
2) There are too many parallel queries.
3) You have set "Max worker threads" to a low value.


Worker threads are set to zero, default.
Post #1482762
« Prev Topic | Next Topic »

Add to briefcase 12345»»»

Permissions Expand / Collapse