At 08:33 AM 15/10/2003 +0200, you wrote:

>Thank you george for the swift reply, although I never thought that
>firebird/ib would have a problem storing millions/billions of records and
>still fetch specific ones in a couple of milliseconds,
>
>however my problem here has nothing to do with the amount of records, we
>have over 100 fields in the table, there are MANY indexes probably more than
>50, selecting a specific record based on the PK is really slow, so I was
>wondering if the problem has anything to do with too many fields and/or too
>many indexes.
>
>We already have done sweeps/backup/restore to try and clean up any garbage
>from the table(s).
>
>This table performs SLOW even with very little data.

Didn't you say this table has only four records? if so, DROP ALL THE INDEXES.

Even better, change the geometry of the data structure. 100 rows of 4
columns, plus a PK and maybe a couple for types or groups, would be much
faster than 4 rows of 100 columns. In future, you would add a new row
instead of a new column...it's called future-proofing. :-) No indexes
needed on a table of 100 rows.

heLen