I found this question here: OLEDB v/s ODBC
Which gave me more information, but did not really answer the question I\'m asking, so I shall proceed from there.
I a
As a C# developer and because you are accessing many different datasources you should go with OLEDB. I copied the following from this white paper because it gives some hints what to use when:
OLE DB is Not a Replacement for ODBC
The ODBC technology and third-party market have matured to a point at which ODBC is an ideal technology for accessing SQL databases. As a result, an integral part of OLE DB is a new OLE DB driver manager that enables OLE DB consumers to talk to ODBC providers. The following information can guide your choice of which technology to use:
- If you are accessing standard relational databases from a non-OLE environment, ODBC is the best choice.
- If you want to expose a data interface to non-SQL data, OLE DB is the best choice.
- If you are programming in an OLE environment, OLE DB is the best choice.
- If want to build interoperable database components, OLE DB is the only choice.