"Lenny Shprekher" wrote:

> Hi,
>
> I am getting issues that Oracle collecting opened sessions (connections)
> from my webservice using regular System.Data.OleDb.OleDbConnection object.
> I am guessing that this is connection pooling issue. Is there is any way to
> disable connection pooling for one particular .net webservice?
>
> Thanks,
> Leonid
>
> BTW: Here is sample connection string we are using:
>
> Provider=MSDAORA.1;Password=test;User ID=test;Data Source=test.tcp;
>
>
>
>

"Cowboy (Gregory A. Beamer) - MVP" <NoSpamMgbworld@comcast.netNoSpamM> wrote
in message news:B873AE57-18C7-4161-BC4F-3E4A62B68085@microsoft.com...
> Yes and no. Connection pooling is based on the entire connection string,
> along with user (if integrated security). Every hit with the same
connection
> pools. If you have the web service in its own web, you can use the config
> file to set up connection properties and be less likely to affect other
> projects. With web services, it is more imperative that you Dispose()
> connection objects when you are done with them.
>
> On a related note, ODP.NET (from Oracle http://otn.oracle.com) is a better
> option than OleDb. The OracleClient is okay, but there are things missing
> from it (written while 9i was still in beta).
>
>
> ---
>
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ***************************
> Think Outside the Box!
> ***************************
>
>
>
> "Lenny Shprekher" wrote:
>
> > Hi,
> >
> > I am getting issues that Oracle collecting opened sessions (connections)
> > from my webservice using regular System.Data.OleDb.OleDbConnection
object.
> > I am guessing that this is connection pooling issue. Is there is any way
to
> > disable connection pooling for one particular .net webservice?
> >
> > Thanks,
> > Leonid
> >
> > BTW: Here is sample connection string we are using:
> >
> > Provider=MSDAORA.1;Password=test;User ID=test;Data Source=test.tcp;
> >
> >
> >
> >