OLE DB ( Connecting and Embedding Objects, Database , sometimes written as OLEDB or OLE-DB ), an API designed by Microsoft, allows accessing data from multiple sources in a uniform way. The API provides a set of interfaces that are implemented using Component Object Model (COM); it is not related to OLE. Microsoft originally intended OLE DB as a higher-level replacement for, and its successor, ODBC, expanded the feature set to support a wider range of non-relational databases, such as object databases and spreadsheets that do not always implement SQL.
Video OLE DB
Methodology
OLE DB separates data storage from applications that require access through a series of abstractions that include data sources, sessions, commands, and rowsets. This is done because different applications require access to different types and data sources, and do not always want to know how to access functionality with specific technology methods. OLE DB is conceptually divided into consumer and provider . Consumers are applications that require access to data, and the provider is a software component that implements the interface and thus provides data to the consumer. The OLE DB is part of the Microsoft Data Access Components (MDAC) stack.
Maps OLE DB
Support status
The release of Microsoft SQL Server 2012 (internal code: 'Denali') is the last one to include the OLE DB provider for SQL Server, but support will continue for 7 years. According to a related Microsoft FAQ, "Providers like ADO.NET that can run on top of OLE DB will not support OLE DB after the last one is no longer used", but the same answer in the FAQ states that the original post only relates to the OLE DB Provider for SQL Server , so the position of OLE DB itself is still unclear. The same FAQ states that ODBC performs better than OLE DB in most cases.
On October 6, 2017 Microsoft announced that the OLE DB was not terminated.
See also
- OLE DB provider
- OLE DB Consumer
References
Source of the article : Wikipedia
0 Comments