Ok let me ask that again - maybe someone intelligent will answer this time

-----Original Message-----
From: <davide_at_davide.clockwork.nl> [mailto:davide_at_davide.clockwork.nl]On Behalf Of davide_at_yahoo.com

>> Use the Microsoft ODBC driver, not the one distributed by Oracle, the
>> MS one is much faster.

Umm - open up the ODBC adminstrator thingy. Select the Oracle supplied ODBC connection. Click CONFIGURE and set the PreFetch Count to something very much higher than one.

If I'm not mistaken, the default is one and this causes one fetch per row returned from the database. If you up it to something more suitable, say 300 then you get (almost) 300 rows returned per fetch. This makes it a lot faster. The problem is that this 300 applies to every table fetched from using that ODBC connection, so may cause memory problems on the client if it is too high and/or the rows are very large.

The M$ driver doesn't have a PreFetch Count, however, it defaults to using a buffer which is 32KB in size and this is where it puts as many rows as it can per fetch into. Regardless of the row size, there is only ever 32KB fetched (by default) so there are less chances for the memory problems mentioned above.

I know this because I spent some time recently testing both ODBC drivers to sort out a problem I was having in using the SQL_ATTR_ROW_ARRAY_SIZE (or something like that) attribute in a program. The Oracle driver was not returning an error, nor was it setting the array size to the requested value.

This is happening in the latest 817 ODBC driver and has been found to be a bug :o)

Cheers,
Norman.

PS. I've missed a lot over the last few days, we had a new firewall installed, and News was no longer working :o( Received on Thu Apr 25 2002 - 09:49:21 CDT