
Oracle Objects vs Oracle ODBC in VB
Quote:
>>writes:
>>> Hi, I have a database set up in Personal Oracle 7. I ran the parallel test
>>> that comes with the Oracle CD-ROM which compares Oracle Object and ODBC in
>>> VB application. The result really surprices me! I have been told that
>>> Oracle Objects are significantly faster the Oracle's ODBC driver. But when
>>> ran the test query which returns about 1000 rows Oracle Object creates the
>>> dynaset a bit faster than ODBC but if I choose to reference the selected
>>> columns (instead of just doing MoveNext), Oracle Object takes more than
>>> double the amount of time to go the result set than ODBC does. This is
>>> true even if I turn off Cashe. Why is that? Does anyone else has the same
>>> experience. I am running Personal Oracle on a 486/66 with 16 MB RAM and
>>> about 12 MB of smartdrive cache. I have a 1 GB hard drive. I am doing a
>>> suming of a column by groupping 2 columns.
>We have had exactly the same experience with Oracles test program. Both with
>PO7 and Oracle running on a dedicated Netware Server.
>It amazed us and our client that Oracle, who poo poos ODBC from a great height
>(in my part of the world at least), would distribute a program that shows ODBC
>outperforming OO4O !!
The test app included with OO4O has the right concept, but you really need
to excercise it to see better performance results. Try using it against
tables with hundreds of columns and thousands of rows.
Try to create a snapshot in VB with millions of rows. Would that even work?
In some ways, OO4O(being OLE Automation based) is slightly ahead of it's
time. It is subject to OLE Automation overhead/intricacies/etc.
Some people say it's much faster, some say it's slower....
OO4O does provide other features over ODBC(assuming you only need to tale
to Oracle) such as:
Read Consistency, Support for Bind Variables, In/Out vars in PL/SQL
stored procedures, Transactional control, full Oracle SQL support,
easily shared connections, etc...
OO4O does not solve all of the problems of ODBC, but it wasn't designed
to do that. Think of OO4O as trying to be take the DAO concepts and
more tightly integrate them into Oracle using the most flexible
technology available (at the time)...
Quote:
>BTW If you are using Oracles ODBC driver, make sure you have a recent version
>(sqlora7.dll 16 Jan 95, sqorast7.dll 21 Oct 94). The earlier version we
>were using had a memory leak - make that a memory gush!
>Regards
>MarkW