Post reply

Does Anybody know what this Error is?

  • April 17, 2008 at 11:14 am

    #121145

    Hi All,

    I have this strange error on my Database server Log.

    startsubprocess: Limit on 'Max worker threads' reached.

    Just as additional Info, this is a subscriber. Does anybody know what this error is? I have this error show up from three different SPIDS.

    Thanks

    Roy

    -Roy

  • April 17, 2008 at 1:08 pm

    #803964

    This error indicates that system is running out of virtual memory. My suggestion would be to check RAM.

    [font="Verdana"]--www.sqlvillage.com[/size][/font]

  • April 17, 2008 at 1:14 pm

    #803968

    Thats almost impossible. It has got 32 GIG as RAM and it has 16 CPUs. It is one of the systems that we call it as a "Server Using Steroids"

    And I did check the RAM and it was using 2 GIG and it still had quite a bit of it.

    PS : The Number of Worker Thread is set as 255.

    -Roy

  • April 17, 2008 at 1:39 pm

    #803984

    You might care to read this:

    http://msdn2.microsoft.com/en-us/library/ms187024.aspx

    Given that document - I would assume that you upgraded a SQL 2000 to 2005. When you do that it retains the max worker threads setting. You may care to change it to 0 (meaning - let the server figure out the right amount).

    255 for a 16-proc server seems way too low to me....

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • April 17, 2008 at 1:41 pm

    #803986

    Can you post output of :

    DBCC SQLPERF (umsstats)

    An additional thing, Since you have 16 CPU on that box so you should configure 352 worker thread (per MS)

    [font="Verdana"]--www.sqlvillage.com[/size][/font]

  • April 17, 2008 at 1:52 pm

    #803991

    Yes, that article does show some light on the issue. I will set it up as MS says and see if I get the error again tomorrow early morning and then restart SQL Server engine.

    Thanks Both of you.:)

    Roy

    -Roy

  • April 18, 2008 at 12:36 am

    #804114

    Great Max....that was an exact answer.....thanks....it proved helpful for me....

    Chandrachurh Ghosh
    DBA – MS SQL Server
    Ericsson India Global Services Limited
    Quality is not an act, it is a habit.

Viewing 7 posts - 1 through 6 (of 6 total)

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