Re: Oracle Objects 4 Ole Performance

From: Keith Majkut <kmajkut_at_netcom.com>
Date: 1995/04/10
Message-ID: <kmajkutD6uDMy.9Iu_at_netcom.com>#1/1


In article <tedh.797315224_at_tdl14>, Ed Henderson <tedh_at_ssi1.com> wrote:
>I tried out Oracle Objects 4 OLE today. My initial opinion is very
>positive. I like the object model, and the performance is much better than
>ODBC.
>
>We have been using a third part package called 2ndwind for Excel. 2ndwind
>provides some custom DLL functions and an Excel interface to Oracle.
>2ndwind copies data from an Oracle database into the windows clipboard,
>where the data can then be pasted into the Excel worksheet.
>
>2ndwind copies the data in 'blocks'. The blocks contain about 64 records
>from the database query.
>
>As a benchmark, I downloaded a database table with 6 columns and 830 rows.
>2ndwind downloaded the entire table into Excel in 13.56 seconds. Using OO4O
>the same download took 1 minutes, 11.5 seconds.
>
>The main reason OO4O is slower is that I must 'place' each fields from each
>row into the spreadsheet individually. I.E.
>
>do while not OraDynaset.EOF
> For i = 0 to numfields - 1
> Range.offset(row,i) = field(i)
> next
> row = row + 1
>loop
>
>As I said before, I really like OO4O. It is much easier to use, the object
>model is great, and it allows query strings to be greater than 255
>characters ( a limitation in 2ndwind). Can anyone at Oracle tell me how to
>squezze the last bit of performance from this otherwise great new
>development?
If you've read the section on "Tuning and Customization" in the online doc, then you have it all. Since OO4O is designed to be a general purpose OLE Automation interface, it does not contain any special purpose Excel features for putting whole rows intos cells, etc...
>
>--
>These opinions are mine, and do not represent those of SSi or TDK.
>Edward Henderson | .. I am come that they might have life,
>ed.henderson_at_tus.ssi1.com | and that they may have it more abundantly.
> | John 10:10b
Received on Mon Apr 10 1995 - 00:00:00 CEST

Original text of this message