Re: Differences between OleDB and IBM.Data DB2 connection

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Generally, one should avoid using OSFA (one-size-fits-all) interfaces like
OLEDB. These add extra layers of interfaces and providers that have to
translate from the generic interface to the specific provider interface and
back for each interaction with the data source. So, yes, I expect the native
managed provider should expose more functionality, be more stable and
probably quite a bit faster. However, don't believe anything I (or anyone)
says about performance. Your actual performance is often gated by issues we
don't know about.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

"ajmastrean" <ajmastrean@xxxxxxxxx> wrote in message
news:1165849187.406866.268660@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Folks,

What are the differences in terms of functionality and performance
regarding connections to a DB2 database using the OleDB provider <
IBMDA400.DataSource.1 > versus an ADO.NET or IBM provided class like <
IBM.Data.DB2.iSeries >.

I am trying to avoid providing extra dll's or classes in a data access
wrapper that needs to connect to several databases (I am wrapping the
Enterprise Library 2.0 data access application block for use in various
projects).

Thanks!



.



Relevant Pages

  • Re: External dialup modem instructions for Maverick
    ... Many more configurations are possible, ... interfaces for more information and supported options. ... leave provider as is, when done if you left "provider" untouched ... connect with pon in terminal poff to disconnect ...
    (Ubuntu)
  • Re: SqlConnection vs IDbConnection
    ... IDbConnection, IDbCommand, and the like are just ... implementations (like SqlConnection, SqlDataReader, SqlCommand, etc, etc). ... for you with the underlying provider. ... programmer suggested I use the IDbConnection, IDbCommand interfaces ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: SqlConnection vs IDbConnection
    ... IDbConnection, IDbCommand, and the like are just ... implementations (like SqlConnection, SqlDataReader, SqlCommand, etc, etc). ... for you with the underlying provider. ... programmer suggested I use the IDbConnection, IDbCommand interfaces ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: CFT: new trunk(4)
    ... 100M interfaces. ... provider, a 100M connection, and we're looking at doing exactly ... switch needs to understand trunking but FreeBSD doesn't. ... physical links rather than dynamically sharing traffic across the ...
    (freebsd-current)
  • Re: nVarchar limitations using OLEDB provider
    ... but not nvarcharor greater using a clientside cursor. ... is IMHO what OLEDB is designed for: ... Unless of course this OLEDB provider is not supported at all..... ... The issue may actually lie on the client code and not on the ...
    (microsoft.public.sqlserver.ce)