title: Speed Difference between native OLE DB and ADO.NET
body: <p>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.  </p>
  
  <p>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.  </p>
  
  <p>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?</p>
  
  <p>Any ideas, or help or places to look on the web would be greatly appreciated. </p>