 | This articlerelies excessively onreferences toprimary sources. Please improve this article by addingsecondary or tertiary sources. Find sources: "OLE DB" – news ·newspapers ·books ·scholar ·JSTOR(April 2012) (Learn how and when to remove this message) |
OLE DB (Object Linking and Embedding, Database, sometimes written asOLEDB orOLE-DB) is anAPI designed byMicrosoft that allows accessingdata from a variety of sources in a uniform manner.[1][2] The API provides a set of interfaces implemented using theComponent Object Model (COM); it is otherwise unrelated toOLE. 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 asobject databases andspreadsheets that do not necessarily implement.
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 intoconsumers andproviders. 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 theMicrosoft Data Access Components (MDAC).
Microsoft's release ofSQL Server 2012 (internal code: 'Denali') is the last to include an OLE DB provider for SQL Server, but support will continue for 7 years.[3] According to a related Microsoft FAQ,[4] "Providers likeADO.NET which can run on top of OLE DB will not support OLE DB once the latter isdeprecated", 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.[5]
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 toODBC drivers,JDBC drivers, andADO.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 asOracle,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 asservices in Microsoft parlance.