Mark,

Before looking at the index/plans etc I would look at the db stats.
Run a gstat against the db and check Oldest Active Trans and Next Trans
differences.
If this is large and you havent backed up/restore in a while - do that ASAP.

Then you will need to find out why you have such a difference.
Applications not committing transactions etc ...

bill

M Patterson, Multinail wrote:

>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
>
>
>
>To unsubscribe from this group, send an email to:
>ib-support-unsubscribe@egroups.com
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>