Hi!

thanks for the info!

> The fact it's not a C/S app is probably the biggest
> performance problem, a query that returns 10 rows
> of 10 fields, will always be faster then one that
> returns 10,000,000 rows of 100 fields, given a database
> that has 10,000,000 rows of 100 fields. Especially
> if the application then has to then figure out the
> 10 rows it really wants.

Oh, it isn't that bad. It is an IBO C/S app, and does use triggers and
stored procedures and everything, but it just isn't fully optimized yet. The
largest tables will have less than 10,000 rows, most of them less than 800.

The worst non-optimized thing is just one location in the application where
it needs to read in the complete primary key column of a table that's up to
10k rows big. Do you know if such a query is satisfied from the PK index?

Thanks.

Cheers,
Tobias