Hmmm ... see I am still reading up on that, but someone threw a wrench saying that there is some limit (500 ot 520) on connections when using odp.net?
I still haven't finished reading everything, thought would poll the collective genius on the list in the meantime.
Cheers and thanks Raj
Your Oracle choices are
1) Shared Server. You can control this. 2) Using the standard features of the connection technology that they will be using anyway. The Oracle Provider for .Net does connection pooling, if they are still with ADO that does connection pooling, if they are still with ODBC then maybe HR might be a bit of an intellectual leap - but yep that does connection pooling. 3) JDBC and a Java App server.
My personal preference would be to use ODP.Net and its connection pooling.
---------------------------------------------- Got RAC? -- //www.freelists.org/webpage/oracle-l