• 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?