Maybe I can shed some more light on the problem Stefan (a colleague of mine) is experiencing
Increasing the max pooled connections to 1000 was just like a shot in the dark. You will see that the pattern it follows is rather weird, so we have tried several weird things to counter the weirdness. OK: Here's the pattern of weirdness The data access class always opens a connection, does the query and closes the connection again (thx to you guys, we now have a couple of extra dispose statements in there as well, made some difference - thx) Environment is: COM+ on winXP. SQL 200 on Win 2000. Development in Vb.NET using the data.sqlclient classes to connect and do queries. The COM+ packages are deployed as "library" We use 12 different databases on the same SQL 2000 box, and as such we thought we would only need 12 pooled connections to service all requests. Sure, we do a couple of thousand data accesses, and in this time we see only 12 to 14 pooled connections being used (reported by perf mon: .NET CLR Data, object: SQLClient # pooled connections). After doing about 1800 queries, it then randomly dies. (it will then halt and the timeout occurs.) Funny thing is, this seems to be process specific: after we get the error, it refuses to do even one more query. You have to restart the process, and the new process then immediately does another 1800 and then dies. If we start 2 processes simultaneously, both do about 1800 queries individually before bogging down. During the "waiting for the timeout" period, the SQL box seems to be idle. We are currently running only one process, and the whole idea is to run about 5 processes per COM+ box and have about 6 COM+ boxes to one SQL box. So, it seems as if we hit some kind of threshold per process/application after about 2000 queries. Any ideas? JC Oberholzer The views expressed in this e-mail are, unless otherwise stated, those of the author and not of SDT or its management. The information is confidential and is intended solely for the addressee. All reasonable steps are taken to ensure the accuracy, integrity and confidentiality of information. No liability or responsibility is accepted if information is corrupted or does not reach its intended destination. This email message has been scanned for viruses and cleared. =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
