Subject What could be slowing our database down?
Author M Patterson, Multinail
Hi,

I'm asking on behalf of a colleague. A customer has our factory management
product running Firebird. It has started running much slower. The file size has
reached 400 MB after about a year of use.

The questions we have are:
Could the presence of indexes significantly slow down our import process? It
consists mainly of INSERTS to the large tables, with say 1 million records.

Could the size of the table (~1M recs) significantly affect the speed of
returning records read by index?

Would it be sensible to split the big table into smaller tables, and either have
duplication or do Union queries as needed?

Would it be sensible to have separate databases?

I expect people to say Need more info, what are the record structures, show me
the plan, etc. But I'm asking in general. What things do people do to speed up
otherwise well designed databases that start running slow? And I'm the Firebird
sponsor at our company, working on a different project now.

Regards,

Mark