Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

what is the difference between ODBC and OleDB? Expand / Collapse
Author
Message
Posted Monday, July 21, 2008 5:53 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 31, 2009 7:47 AM
Points: 15, Visits: 95
Hi Friends

what is the difference between ODBC and OleDB?
Post #537592
Posted Monday, July 28, 2008 9:33 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 28, 2008 9:30 AM
Points: 1, Visits: 0
ODBC-it is designed for connecting to relational databases.
However, OLE DB can access relational databases as well as nonrelational databases.

There is data in your mail servers, directory services, spreadsheets, and text files. OLE DB allows SQL Server to link to these nonrelational database systems. For instance, if you want to query, through SQL Server, the Active Directory on the domain controller, you couldn't do this with ODBC, because it's not a relational database. However, you could use an OLE DB provider to accomplish that.

In summary, The key difference between OLE DB and ODBC is that OLE DB can provide connection to data stored in non-relational format.
:)
Post #541974
Posted Monday, July 28, 2008 9:50 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 5:59 PM
Points: 31,082, Visits: 15,529
Good explanation. OLEDB is newer and superceeds ODBC. You should aim to use OLEDB connections where possible. I believe there's an OLEDB provider that encapsulates all ODBC functionality.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #541991
Posted Monday, October 8, 2012 8:11 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 5:12 PM
Points: 300, Visits: 310

Though, this discussion had been an old discussion, I just want to add the information I got regarding OLD DB drivers. As per the below article, Microsoft is planning to depreciate OLEDB APIs and SQL Server 2012 will be the last version to support OLEDB. Therefore, it is highly recommended for programmers to write their codes with ODBC compatibility than OLEDB.

http://www.itwriting.com/blog/4825-full-circle-for-microsoft-database-apis-as-ole-db-for-sql-server-is-deprecated.html
Post #1369839
Posted Tuesday, October 9, 2012 3:06 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:10 PM
Points: 5,103, Visits: 11,906
Steve Jones - SSC Editor (7/28/2008)
Good explanation. OLEDB is newer and superceeds ODBC. You should aim to use OLEDB connections where possible. I believe there's an OLEDB provider that encapsulates all ODBC functionality.


Steve, I think this may not be the best advice.

Looks to me as though OLEDB is being deprecated. Here's another link which discusses the topic.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1370239
Posted Tuesday, October 9, 2012 4:49 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 9:38 AM
Points: 2,858, Visits: 5,132
Phil Parkin (10/9/2012)
Steve Jones - SSC Editor (7/28/2008)
Good explanation. OLEDB is newer and superceeds ODBC. You should aim to use OLEDB connections where possible. I believe there's an OLEDB provider that encapsulates all ODBC functionality.


Steve, I think this may not be the best advice.

Looks to me as though OLEDB is being deprecated. Here's another link which discusses the topic.


That was actually interesting link to read. Especially the part about
Microsoft has been supporting ODBC through all the releases of SQL Server for relational data access. This includes adding new functionality to the ODBC drivers whenever a corresponding feature is added to SQL Server.

I've developed an application few years ago, which needed to receive and display in GUI long stored procedure progress. Progress messages were implemented in stored proc using RAISERROR (of message severity) WITH NOWAIT which allows receiving such messages asynchronously by the client. It is possible using ADO InfoMessage handling. But, I only managed to get it working properly using ODBC driver! All other drivers, for some reason, would get all InfoMessage events accumulated and raised at once on the end of process. I was really surprised that time why "old" ODBC driver did work but newest SQL Server Native Client didn't...
Looks like MS always treated ODBC as the most up-to-date driver.


_____________________________________________
"The only true wisdom is in knowing you know nothing"
"O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!"
(So many miracle inventions provided by MS to us...)

How to post your question to get the best and quick help
Post #1370308
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse