16 KB page size is ok and is maximal for FB1.5 to FB3.
During problem time run gfix -h and show us the results and also gstat results
for that tabe and indexes on it.
P.S. to recreate index you do not need to set it inactive. You can activate
already active index. But this operation can be done
Thanks Helen. Just a few clarifications, that might help whittle this down a
bit...
>Given that this table is "temporary" storage, one supposes that you
are deleting rows from it regularly. Do you happen to be deleting
900,000 rows each day before you load up the latest batch of 900,000?
Myles Wakeham wrote:
> The issue is with one very large table that contains about 900,000
> rows. This table is used as a temporary stora ge of data that is
> loaded every 24 hours from a CSV file, via an external program. The
> loading takes about an hour to run, but works reliably. We are
Thank you for your comment. Very helpful. I ran gstat on the database, and on
the table in question. It is the default 16K page size. Are you saying that a
larger page size would be more appropriate? If so, how large would you
suggest? And is it correct that the only way to change the
Hi.
Run gstat and look at info about this table.
Look also at page size of your database. It can be small in 1.5 version, if
yes, change it to bigger value especially 16K.
PS. 900,000 rows is quite small table also for Firebird 1.5
regards,
Karol Bieniaszewski
Thanks for your reply. The problem isn't that what you are saying *should* be
done. The problem is that this database has over 200 tables, and 1200 stored
procedures and the process to do it is long (ie. over a month of work likely).
I did manage to get a solution here by converting all
I have a client with a Firebird 1.5 Classic server that is in the process of
being upgraded to a later version. The database is quite complex and this
upgrade will take some time. However the database has been working well for
the past 8 years, and just in the past few weeks we have seen
