Subject | Re: [firebird-support] Slow table after many updates |
---|---|
Author | Helen Borrie |
Post date | 2005-12-16T22:07:08Z |
At 02:02 PM 16/12/2005 +0000, you wrote:
don't have much RAM available).
2. Avoid tools or application code that use CommitRetaining (used by a lot
of third-party tools by default)
3. Don't design a system that has a bottleneck for controlling unique
keys. Ideally, generate the unique keys using a generator.
./heLen
>Hello all!..or of your application code?
>
>I have a table for control the unique keys (code) of all my tables.
>I have been importing data for my database and there are a lot of
>updates in a register in this table. +/- 1.000.000 of updates.
>After many update this table get slow, very slow. And I can't get a
>backup, the backup stop in this table. And is very, very slow to open
>the data of this table.
>This is a very bad feature of firebird.
>What could I do for the table doesn't get slow?1. Hard Commit at reasonable intervals. (~ 8000 inserts, or less if you
don't have much RAM available).
2. Avoid tools or application code that use CommitRetaining (used by a lot
of third-party tools by default)
3. Don't design a system that has a bottleneck for controlling unique
keys. Ideally, generate the unique keys using a generator.
./heLen