0% found this document useful (0 votes)
75 views

Ole DB

OLE DB is an API designed by Microsoft that allows accessing data from various sources uniformly. It separates data stores from applications through abstractions like datasources, sessions, commands, and rowsets. OLE DB providers enable consumers to interact with data sources and can access simple data stores like spreadsheets or complex databases like SQL Server.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
75 views

Ole DB

OLE DB is an API designed by Microsoft that allows accessing data from various sources uniformly. It separates data stores from applications through abstractions like datasources, sessions, commands, and rowsets. OLE DB providers enable consumers to interact with data sources and can access simple data stores like spreadsheets or complex databases like SQL Server.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

OLE DB

OLE DB (Object Linking and Embedding, Database, sometimes written as OLEDB or OLE-DB), an
API designed by Microsoft, allows accessing data from a variety of sources in a uniform manner. The API
provides a set of interfaces implemented using the Component Object Model (COM); it is otherwise
unrelated to OLE. Microsoft originally intended OLE DB as a higher-level replacement for, and successor
to, ODBC, extending its feature set to support a wider variety of non-relational databases, such as object
databases and spreadsheets that do not necessarily implement.

Contents
Methodology
Support status
OLE DB providers
References

Methodology
OLE DB separates the data store from the application that needs access to it through a set of abstractions
that include the datasource, session, command, and rowsets. This was done because different applications
need access to different types and sources of data, and do not necessarily want to know how to access
functionality with technology-specific methods. OLE DB is conceptually divided into consumers and
providers. The consumers are the applications that need access to the data, and the providers are the
software components that implement the interface and thereby provides the data to the consumer. OLE DB
is part of the Microsoft Data Access Components (MDAC).

Support status
Microsoft's release of SQL Server 2012 (internal code: 'Denali') is the last to include an OLE DB provider
for SQL Server, but support will continue for 7 years.[1] According to a related Microsoft FAQ,[2]
"Providers like ADO.NET which can run on top of OLE DB will not support OLE DB once the latter is
deprecated", but the same answer in the FAQ states that the original post relates only to the OLE DB
provider for SQL Server, so the position of OLE DB itself remains unclear. The same FAQ states that
ODBC performs better than OLE DB in most cases.

However, during subsequent reviews it was determined that deprecation was a mistake because substantial
scenarios within SQL Server still depend on OLE DB and changing those would break some existing
customer scenarios. On Oct 6, 2017 Microsoft announced that OLE DB was undeprecated, and a new
version to maintain dependencies would be released in early 2018.[3]
OLE DB providers
An OLE DB provider is a software component that enables an OLE DB consumer to interact with a data
source. OLE DB providers are analogous to ODBC drivers, JDBC drivers, and ADO.NET data providers.

OLE DB providers can be created to access such simple data stores as a text file and spreadsheet, through
to such complex databases as Oracle, Microsoft SQL Server, Sybase ASE, and many others. It can also
provide access to hierarchical data stores such as email systems.

However, because different data store technologies can have different capabilities, every OLE DB provider
cannot implement every possible interface available in the OLE DB standard. The capabilities that are
available are implemented through the use of COM objects; an OLE DB provider will map the data store
technologies functionality to a particular COM interface. Microsoft describes the availability of an interface
as "provider-specific," as it may not be applicable depending on the data store technology involved.
Providers may augment the capabilities of a data store; these capabilities are known as services in Microsoft
parlance.

References
1. Microsoft SQLNCli team blog: Microsoft is Aligning with ODBC for Native Relational Data
Access (http://blogs.msdn.com/b/sqlnativeclient/archive/2011/08/29/microsoft-is-aligning-wit
h-odbc-for-native-relational-data-access.aspx)
2. SQL Server Forums - SQL Server Data Access: Microsoft is Aligning with ODBC for Native
Relational Data Access (http://social.technet.microsoft.com/Forums/en/sqldataaccess/threa
d/e696d0ac-f8e2-4b19-8a08-7a357d3d780f)
3. Microsoft SQLNCli team blog: Announcing the new release of OLE DB Driver for SQL
Server (https://blogs.msdn.microsoft.com/sqlnativeclient/2017/10/06/announcing-the-new-rel
ease-of-ole-db-driver-for-sql-server/)

"OLE DB Providers Overview" (http://msdn.microsoft.com/en-us/library/ms709836%28v=vs.8


5%29.aspx). Microsoft. MSDN: Data Developer Center. Retrieved March 23, 2011.

Retrieved from "https://en.wikipedia.org/w/index.php?title=OLE_DB&oldid=1030984884"

This page was last edited on 29 June 2021, at 03:59 (UTC).

Text is available under the Creative Commons Attribution-ShareAlike License 3.0;


additional terms may apply. By
using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the
Wikimedia Foundation, Inc., a non-profit organization.

You might also like