ODBC Parameter Array Size > 1 causes failure

[AlanP]

Hi

We have been trying to optimise some jobs that run over a WAN link. When running on development, we typically get between 1000-2000 rows/sec. Over the WAN link this drops to 60 rows/sec. Upping the Array size > 1 has helped, sometimes cutting job times to 1/20th the elapsed time.

However, we have one job with a lot of columns, containing timestamps and fractional values that gives a 'Fractional truncation' error unless the array size is kept at 1.

Any ideas?

[ArndW]

That is a strange scenario. The array size should not have any knowledge of the data types, just the row and block sizes. Can you narrow down your error to a single column and perhaps even to a single value for that column?