Hi,

I'm just about to port a ..Net database application to Oracle. from what I
can see, the obvious two choices are ODP.NET (a free download from oracle)
and System.Data.OracleClient which seems to be built in to the bloatware,
erm, I mean framework.

Any reason to choose ODP.NET over the built-in one? are there any options
which are to be preferred? I'm not after the ultimate in performance, just
to use the de-facto standard which will give me least hassle and best
portability

Andy

"Andy Fish" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I'm just about to port a ..Net database application to Oracle. from what I
> can see, the obvious two choices are ODP.NET (a free download from oracle)
> and System.Data.OracleClient which seems to be built in to the bloatware,
> erm, I mean framework.
>
> Any reason to choose ODP.NET over the built-in one? are there any options
> which are to be preferred? I'm not after the ultimate in performance, just
> to use the de-facto standard which will give me least hassle and best
> portability
>
> Andy
>
As you seem to dislike the .NET Framework, why not really port the
application using Oracle development tools? That'll really give you
something to complain about
Since you appear to be asking about connecting an existing .NET application
to an Oracle database, I'd suggest using the Oracle alternative as the it
will typically be available for the specific version of the DBMS you intend
to connect to, and will probably give you access to more DBMS features.
YMMV.

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.

On Tue, 9 Aug 2005 11:33:53 +0100, "Andy Fish" <(E-Mail Removed)> wrote:

¤ Hi,
¤
¤ I'm just about to port a ..Net database application to Oracle. from what I
¤ can see, the obvious two choices are ODP.NET (a free download from oracle)
¤ and System.Data.OracleClient which seems to be built in to the bloatware,
¤ erm, I mean framework.
¤
¤ Any reason to choose ODP.NET over the built-in one? are there any options
¤ which are to be preferred? I'm not after the ultimate in performance, just
¤ to use the de-facto standard which will give me least hassle and best
¤ portability

Just from a historical perspective, the Oracle versions of database drivers and providers are better
supported. However, I've also run into more problems using them. I can't speak to the stability of
ODP.NET because I haven't used it. I'm aware of at least one issue with the Microsoft .NET provider
for Oracle that involves CLOB data types and unicode.

The only main issue I am aware of with respect to ODP.NET is that you must be running the Oracle 9i
client version or higher.


Paul
~~~~
Microsoft MVP (Visual Basic)