Speed Difference between native OLE DB and ADO.NET
Posted
by weijiajun
on Stack Overflow
See other posts from Stack Overflow
or by weijiajun
Published on 2010-04-07T02:37:25Z
Indexed on
2010/04/07
2:43 UTC
Read the original article
Hit count: 482
I'm looking for suggestions as well as any benchmarks or observations people have. We are looking to rewrite our data access layer and are trying to decide between native C++ OLEDB or ADO.NET for connecting with databases. Currently we are specifically targeting Oracle which would mean we would use the Oracle OLE DB provider and the ODP.NET.
Requirements: 1. All applications will be in managed code so using native C++ OLEDB would require C++/CLI to work (no PInvoke way to slow). 2. Application must work with multiple databases in the future, currently just targeting Oracle specifically.
Question: 1. Would it be more performant to use ADO.NET to accomplish this or use native C++ OLE DB wrapped in a Managed C++ interface for managed code to access?
Any ideas, or help or places to look on the web would be greatly appreciated.
© Stack Overflow or respective owner