8 replies
by bill_h
IMHO, the biggest drawbacks are lower performance, and a higher degree of complexity in development. I have found using ADO and OLEDB to be superior. The 'Microsoft OLE DB Provider for Oracle' works quite well. Oracle has released a BETA version of its own provider - my inital experiments have uncovered a few differences in implementation from the MS provider, but no major problems.
For a comparison of data access options, you may wish to view the MSDN article 'Choosing a Data Access Strategy', which can be found at:
http://msdn.microsoft.com/library/devprods/vs6/vstudio/vsentpro/veconchoosingdataaccessstrategy.htm
(The above link may have wrapped...)
Hope this helps...
by dstone9
Although ODBC is often mentioned as being slower than native connections, I have found the performance of ODBC and native Oracle drivers to be about the same.
Native drivers may have a disadvantage when you are using a 4GL development environmentlike PowerBuilder. The SQL code and Datawindows generated by PowerBuilder when connected to an Oracle database through a native driver may be less portable than the same code generated with an ODBC driver.
HTH,
Doug
by fofa
by sfernandez
1. Native Oracle API will tie you to Oracle alone, ODBC stands a reasonable chance of being kept portable.
2. ODBC does not expose all of the features of Oracle 8 (or any other native DB API). For example, management APIs for servers.
3. ODBC datatypes do not exactly match those implmented in every database. There are some datatypes you need to do workarounds for.
Stephen
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending