OracleConnection.State v/s OleDbConnection.State
- From: "John Mark Howell" <jmarkhowell@xxxxxxxxxxx>
- Date: Fri, 18 Nov 2005 11:16:26 -0600
According to the MSDN:
Avoid Accessing the OleDbConnection.State Property
If the connection has been opened, OleDbConnection.State property makes the
native OLE DB call IDBProperties.GetProperties to the DATASOURCEINFO
property set for the DBPROP_CONNECTIONSTATUS property, which may result in a
round trip to the data source. In other words, checking the State property
can be expensive. So only check the State property when required. If you
need to check this property often, your application may perform better if
you listen for the StateChange event for your OleDbConnection. For details
on the StateChange event, see Working with Connection Events.
What I'm wondering is, does the OracleConnection suffer from the same
performance problem? Does it drop down to the IDBProperties as well?
Anyone?
.
- Prev by Date: Re: Simple Question
- Next by Date: Problem with wrong data in dataset using SQLDataAdapter.fill
- Previous by thread: Using the column of a datatable as a paramter for a command object
- Next by thread: Problem with wrong data in dataset using SQLDataAdapter.fill
- Index(es):
Relevant Pages
|
|
