Re: Oracle.DataAccess.Client vs. System.Data.OracleClient -- use which?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Miha Markic [MVP C#] (miha)
Date: 02/12/04 

Date: Thu, 12 Feb 2004 18:20:42 +0100

Hi Ruffin,

MS' provider requires 8.1.7 version while Oracle's require 9i r2 Oracle
client.
Plus, Oracle's provider has few more features.
I would stick with MS - I would use Oracle's provider only when necessary. 

-- 
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com
"Ruffin Bailey" <kaboom@atari.net> wrote in message
news:172e9d35.0402120744.f5f048@posting.google.com...
> When I started working on an ADO.NET application that accessed Oracle
> 9 on the backend, I downloaded and installed ODP.NET from Oracle
> (http://otn.oracle.com/tech/windows/odpnet/index.html) which gave me
> the Oracle.DataAccess.Client namespace.
>
> Was impressed that the Oracle objects were in the VS.NET Help app --
> until I finally figured out that's b/c there's a
> System.Data.OracleClient in .NET 1.1 by default.
>
> Other than a few minor syntax changes (like OracleDbType not existing
> in System.Data.OracleClient), they seem to be the same thing.
>
> Is there any technical reason to use one over the other?  Though it's
> a minor nuisance to install ODP.NET everywhere I install the app, I
> will if that's a better route.  If everything's equal, give or take,
> however, I'll stick to the System.Data.OracleClient just for
> simplicity's sake -- I guess.  Still not completely convinced I
> shouldn't use ODP.NET just so that I've got the vendor's data
> connection code instead of something ultimately from a third party.
>
> Thanks,
>
> Ruffin Bailey

Relevant Pages

  • Re: Cant get Oracle OLE DB provider to work from SSIS on a 64-bit environment
    ... The project I'm trying to get running, consists of approx 25 seperate packages where 3-4 of them gets data from different Oracle sources, but I'm not even got to the point where I'm trying to run the whole lot. ... There are two issues in the topic that could be an issue, and that is to switch the whole project to 32-bit mode and then the part that says that the Designer only shows 32-bit versions of the provider. ... What I think I'll try now, it to install the 32-bit version of the Oracle ODAC to see if that makes any difference. ... uninstall ODAC and when I uninstall the regular Oracle Client with the ...
    (microsoft.public.sqlserver.dts)
  • Re: Cant get Oracle OLE DB provider to work from SSIS on a 64-bit environment
    ... If the 32-bit driver worked well for you, you can have your SSIS package run ... I'm having some troubles setting up an Oracle datasource on a SSIS ... Since this Provider isn't available in the 64-bit version I ... I'd love to uninstall both Oracle clients and then try just to install ...
    (microsoft.public.sqlserver.dts)
  • Cant get Oracle OLE DB provider to work from SSIS on a 64-bit environment
    ... I posted this question in the .server newsgroup yesterday, but apparently my cross-post to this newsgroup didn't made it, so now I post it once more. ... I'm having some troubles setting up an Oracle datasource on a SSIS ... Since this Provider isn't available in the 64-bit version I ... I'd love to uninstall both Oracle clients and then try just to install ...
    (microsoft.public.sqlserver.dts)
  • Re: More question on OLE DB
    ... How about MSDAORA and SQLOLEDB.1, ... machine need to install to have MSDAORA and/or SQLOLEDB.1? ... Oracle has it's own provider. ...
    (microsoft.public.vb.general.discussion)
  • Oracle.DataAccess.Client vs. System.Data.OracleClient -- use which?
    ... When I started working on an ADO.NET application that accessed Oracle ... Was impressed that the Oracle objects were in the VS.NET Help app -- ... Other than a few minor syntax changes (like OracleDbType not existing ... a minor nuisance to install ODP.NET everywhere I install the app, ...
    (microsoft.public.dotnet.framework.adonet)