truble!Oracle with adonet

  • Thread starter Thread starter tiger liu
  • Start date Start date
T

tiger liu

Oracle 8.17
Code as follewed :

dim objCnn as OleDbconnection=new ....
objCnn.open()
objCnn.close()

objCnn=nothing

but the connection is still found by oracle ! How could i do?

and driver providered by oracle.
 
Tiger,

Many people have found this problem in differing circumstances - it comes
from the Connection Pooling in database access. When you close a connection
object, the actual connection is in fact held open for a period of time,
just in case your process wishes to reuse it later. On Oracle databases
this can vastly increase throughput, since Oracle takes (on my tests)
upwards of 700ms to make a new connection.

However, it can lead to problems if you are actually very strict in your use
of connections, for example in a two-tier applications. You can switch off
OleDB connection pooling by the connection string option OLEDB_SERVICES=-4,
or by adding a OLEDB_Services registry key for the OleDB provider in
question.

(search MSDN library for OLEDB_Services for more information).

Hope this helps,

Neil.
 
For oracle we recommend you use the Oracle managed provider, in this
provider to turn off pooling instead of the Oledb services you need to add
"Pooling=false" to your connection string.

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

Neil McKechnie said:
Tiger,

Many people have found this problem in differing circumstances - it comes
from the Connection Pooling in database access. When you close a connection
object, the actual connection is in fact held open for a period of time,
just in case your process wishes to reuse it later. On Oracle databases
this can vastly increase throughput, since Oracle takes (on my tests)
upwards of 700ms to make a new connection.

However, it can lead to problems if you are actually very strict in your use
of connections, for example in a two-tier applications. You can switch off
OleDB connection pooling by the connection string option OLEDB_SERVICES=-4,
or by adding a OLEDB_Services registry key for the OleDB provider in
question.

(search MSDN library for OLEDB_Services for more information).

Hope this helps,

Neil.
Click to expand...
 
Neil,
Thank you!

tiger liu
Neil McKechnie said:
Tiger,

Many people have found this problem in differing circumstances - it comes
from the Connection Pooling in database access. When you close a connection
object, the actual connection is in fact held open for a period of time,
just in case your process wishes to reuse it later. On Oracle databases
this can vastly increase throughput, since Oracle takes (on my tests)
upwards of 700ms to make a new connection.

However, it can lead to problems if you are actually very strict in your use
of connections, for example in a two-tier applications. You can switch off
OleDB connection pooling by the connection string option OLEDB_SERVICES=-4,
or by adding a OLEDB_Services registry key for the OleDB provider in
question.

(search MSDN library for OLEDB_Services for more information).

Hope this helps,

Neil.
Click to expand...
 
angelsa,
thank you!

Angel Saenz-Badillos said:
For oracle we recommend you use the Oracle managed provider, in this
provider to turn off pooling instead of the Oledb services you need to add
"Pooling=false" to your connection string.
Click to expand...
 
Back
Top