Re: Samplclnt example in MDAC 2.8: My Story

Michael Skelton (mskelton@xxxxxxxxxxxxx) writes:
> Sounds great. My question to you would be, why is Microsoft moving
> forward with support of two different data access strategies, ODBC and
> OLE DB? It's funny how Microsoft appears to be pushing OLE DB hard, yet
> people seem reluctant to abandon ODBC, and again, I've heard from
> numerous sources that ODBC still outperforms OLE DB, which is the newer
> technology (!).
>
> This whole story began with my curiosity about OLE DB, and trying to
> explore its utility. My exploration was quickly halted by the age & (in
> my opinion) poor quality of the MDAC SDK's OLE DB sample source code. I
> reiterate my question: if MS is serious about gaining a foothold with
> OLE DB, why does their latest release of the MDAC SDK fail to compile
> with the most recent IDE? Why are there no newer samples than those
> written circa 1998?
>
> ODBC 1, OLE DB 0.

Which may be a correct observation.

There certainly were the days when Microsoft saw OLE DB as the cutting
edge, but these days we have .Net and SqlClient.

At PASS I attended a presentation on SQL Native Client, which is a component
on SQL 2005 that has a both an updated OLE DB provider and an update ODBC
driver for SQL 2005, all in the same DLL. The presenter, Chris Lee, said
that ODBC is a more natural choice for implementing clients in native
code, because the interface is simpler to use. And for SQL Native Client
they've managed to improve the performance for the ODBC side with 20%,
whereas the OLE DB side is equal to he old SQLOLEDB.

OLE DB still has its place - if you have a set of data that you wish
to access as a linked server from SQL Server, you need to implement an
OLE DB provider.


--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.

Relevant Pages

  • Re: Different empty_string/NULL handling under ODBC and OLE DB?
    ... NULL whereas empty string is stored as a space. ... When migrating from ODBC to OLE DB we get errors when inserting an ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Re: What is the faster way to insert/buck insert rows into SQL Server
    ... I would have said SqlClient would be the fastest--that or DBLib. ... Hitchhiker's Guide to Visual Studio and SQL Server ... code in C++ and used ODBC driver SQLBindParameter to bind the data in the ... OLE DB .Net ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Is ADO.NET OleDb .NET Data Provider a COM object?
    ... Okay, okay... ... OLE DB is a one-size-fits-all set of providers that can access anything from a relational database to a tuna salad. ... in order to access SQL Server we used OLE DB to access ODBC or SQL Server. ... In a similar way, just because you can connect to MySQL, Paradox, Oracle or FarkleStar databases from an OLE DB or other OSFA provider does not mean your code can interface with these other back-ends. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Q: what is the relation between DB-Lib, OLE-DB, and ODBC?
    ... >> I had reason some time ago to make a choice between ODBC and OLE DB ... can you recommend any sources of decent sample code for this (OLE ... > DB with MS Sql server), and also, while we're here, on writing extended ...
    (microsoft.public.data.oledb)
  • Re: SqlServer 2005 Transfer Flame
    ... database between the two servers. ... I do understand your concerns with SQL Server 2005. ... Drag a OLE DB Destination to the panel; ...
    (microsoft.public.sqlserver.dts)