Home Forums SQL Server 2008 SQL Server 2008 Performance Tuning Running out of workers RE: Running out of workers

  • October 4, 2013 at 2:06 pm

    #1656045

    ELLEN-610393 (10/3/2013)

    Gail,

    I see that you said that the default 0 for worker threads should be good. What is the impact of having a process spin up several thousand worker threads? Today I was looking at the Activity Monitor and saw that there were two different processes that each had about 3,000 worker threads. This is a new system for me and I was thinking that might be bad.

    We are using SQL Server 2008 R2 SP1, Enterprise 64-bit, 4 processors , 146 GB RAM

    All opinions are welcomed.

    Thank you.

    That, my friend, sounds like a "connection leak" somewhere in the code for those two processes or the code that controls those two processes and both will certainly need to be repaired.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)