Thanks for the reply William but we aggreed to change our perspective.



Yes we are using SPT and we do not use any stored procedure. The Database is not ours we are interfacing with another software's database. We always fetch with Primary key. They do not use indexes (execpt for the PK)

When we did the testing it's really a question of Bandwith. (Each Export is taking 60K and the reason why it's taking longer for multiple export is because since we are taking a lot of bandwith on a overused network link we are loosing performance over Long connection)

We have establish a new solution that will be installing a multi-tier application on the Oracle server so we won't need to send all those validation back and foward. With that we hope to be gaining performance by stopping our network usage and using more processor on the Oracle box.



>Heya Mario -
>is your oracle spt thingie optimized ? check your oracle schema for the db.
>1. are you using a primary key for update/fetch ?
>2. if you are doing inserts, is there a stored proc / trigger that is firing on the backend?
>
>can you provide an example of one of your spt's ?
>
>Typically - I try to match up what ever is in the where clause
>with columns on a back end that are indexed.
>If a column is not indexed, then on a fetch - you will kick the db server into table scan mode.
>
>on an update - it will be a bit slower too - but not as slow as a tablescan
>
>on an insert - it won't matter [usually]
>
>mondo regards [Bill]