Oracle Providers for ADO.NET 2

  • Thread starter Thread starter Eric
  • Start date Start date
E

Eric

We're starting a big project now (using 1.1) and I want to use the best
provider option with an eye towards ADO.NET 2.0.

I have been using the Microsoft Oracle Provider, but I heard that
Oracle's ODP is better for using the advanced database features. I
don't need those features right now, but I don't know about my future
needs.

I also read that Oracle is working with Microsoft on having better
Oracle support in 2.0. I understand the Server Explorer will be more
Oracle-friendly, for example.

Does this mean the Microsoft Oracle provider will also be enhanced?

Will Oracle's ODP be enhanced for 2.0 also, or is that being dropped in
favor of a single provider that will be a joint effort from the 2
companies?

My main concern is that we pick the right choice now so we won't have
to make major code changes later.

Thanks!
Eric
 
The OracleClient namespace objects were created under 8i, so they are quite
old. In 2.0, the push is for newer objects. This will work, for awhile. If
you can use ODP.NET, it is a better option, although I do not know if ODP.NET
is going to have the full wrapper classes that allow you to drag and drop and
set all data bits declaratively.

If you code against the object model present now, you can switch most of the
code back and forth from ODP to OracleClient without any problems. There are
some advanced features in ODP that are not present in OracleClient, but the
majority of your day to day work can be accomplished in either.

If you are using the DataSource objects (not sure if they are present in the
beta builds for Oracle), you will have different models if ODP is not
updated. I am not overly fond of the drag and drop model for most of the
types of apps I build, so I will not have major rework either way I go.

To avoid major refactoring, have your data layer handle the specifics (using
ADO.NET versus ODP.NET, etc.) and the business and UI tier consuming
DataSets. This is the most flexible set up, as you can move back and forth
with changes in one place only. And, you can refactor to the DataSource
objects without a huge amount of pain.
---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
Back
Top