


NET to COM and vice versa including locking/unlocking/converting pointers.ĭon't listen to anyone that makes false accusations about OleDB's performance without understanding how they tested it and what environment they used (managed code vs managed code). The COM interop layer takes care of marshalling passing messages from. NET types and converting the oledb buffer to row and column bindings. The abstraction layer takes care of resource management such as managing memory handles to ensuring that garbage collection occurs correctly, changing data types and parameters to. The drivers for OLEDB are written in native unmanaged code however, when you access these drivers through ADO.NET, you have to go through several layers (including an abstraction layer and a COM interop layer). OLEDB is much faster than the SQLClient, EXCEPT when it is access through ADO.NET.
