Post reply

Connections: How many is too many?

  • February 10, 2004 at 9:29 am

    #493416

    No.  See http://support.microsoft.com/?id=319942

    Updating to SQL Server 2000 will probably increase your performance.  



    --Jonathan

  • February 10, 2004 at 9:38 am

    #493419

    Do you see "The working thread limit of 255 has been reached" in SQL Server error log?

  • February 10, 2004 at 9:53 am

    #493428

    We are running SQL Server 2000.

    I do not see "The working thread limit of 255 has been reached" in SQL Server error log.

    So, what you are saying is my performance problems are probably related to something else than the 350 connections and that changing the "max worker thread" would be a bad idea?

    Is 350 or more concurrent connections on a SQL Server fairly standard?

     

  • February 10, 2004 at 9:59 am

    #493430

    According to the link Jonathan posted, you shouldn't adjust it.

    As suggested in previous posts, You should look into whole system performace and try to identify the bottlenecks.

     

  • February 10, 2004 at 10:04 am

    #493434

    Alright, I think that is what I will do.

    Do you agree though that I will have better performance if I can programmatically keep my connection limit below the 255 default for "max worker threads"?

    Thanks for all the help

Viewing 5 posts - 16 through 19 (of 19 total)

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