What does ODBC have over OLEDB?

Answer 1

ODBC is older than OLEDB but is an Industry standard supported by almost everybody. OLEDB is Microsoft only. OLEDB does come with an interface driver itself so you could do the following if you had to.

OLEDB is the successor to ODBC, a set of software components that allow a "front end" such as GUI based on VB, C++, Access or whatever to connect with a back end such as SQL Server, Oracle, DB2, mySQL etal. In many cases the OLEDB components offer much better performance than the older ODBC.


OLEDB is a different type of data provider that came about with MS's Universal Data Access in 1996 and does not require that you set up a DSN. It is commonly used when building VB apps and is closely tied to ADO. It works with COM, and DCOM as of SQL 7.0.

Answer 2

ODBC has over OleDB that it can work on any DBMS.
ODBC is the very base and generic DB driver and it lacks optimization for a specific DBMS;
In general, it's not recommended to use ODBC.
OLEDB is a higher level of optimization for certain DBMS drivers.
For instance, in ADO.NET there exists 3 layers:
SqlServer, OleDb and Odbc;
If using Oracle, DB2, MySql ...etc. then OleDb should be applied; if using SqlServer 6.5 or above, then SqlServer layer, else OleDb;
ODBC would work with all, but it's not optimized specifically for certain drivers.
Try to find the specific driver for your target DBMS instead of using ODBC.

Answer 3

- both can get admission to community and distant database - ODBC does no longer necessarly require a DSN - There are ODBC for non-relational source. Microsoft as an party provides you ODBC drivers for Excel and undeniable textual content information. you do not opt to position in any particular drivers to get admission to sq. Server from a living house windows app via both OLEDB or ODBC. the biggest adjustments that i be conscious of of between ODBC and OLEDB are that OLEDB is swifter, yet ODBC is more advantageous elementary, you'll locate ODBC connectors for a much broader variety of datasources.