The article is good, but does not really answer the question. OLEDB is a set of COM interfaces that can actually be implemented in .NET through COM Interop, although I have never heard of such an implementation and are probably not recommended.
The OLEDB interface suite is documented by Microsoft here . OLEDB is a complex topic, and not all interfaces are necessary to implement a functional provider. To make matters worse, different OLEDB clients have a set of interfaces that they need to be able to use a provider. For example, here is a list of required interfaces that must be implemented to use the provider from the .Net OLEDB client (System.Data.OleDb. *). Note. I did not find such a link for 2.0 Framework or later. Finally, it is worth noting that it was difficult to implement the vendors that Microsoft later provided the ATL Template Set (C ++) to help developers do it right.
To learn more about OLEDB, I definitely recommend looking at the Windows Data Access SDK on MSDN.
source share