I need to have a table to log detailed user-activities. The
information to be logged are what user, at what time, with what
program does what activity with what data.

So over the time this table holds about 2.5 mio. records and growes to
nearly 6GB ( six ) in Log.mkd, Log.^01 and Log.^02. The table has an
autoincrement-key, a key on the time-stamp and some other keys.
Records are only inserted, no delete and no update. And of course most
of the indexes only will grow. The autoincrement-key always grows, the
time-stamp always grows and some other keys do so too.

This table is created with index-balancing ON.

So reading the table for some reports is quit quick and writing seems
to be quit quick too, but sometimes a single insert takes about 5
minutes ( five ) and more to complete. While this time all the other
clients seems to be locked too.

So here is my question:

Could it be, that re-balancing the indexes can take such a long time
??
Can this operation affect other clients in this way ??

Any helf ist welcome,

Ralf

How big of a database cache do you use, and with which version of the
database engine?

Anytime the files are allowed to grow very large, the indexing structure
gets less efficient, ESPECIALLY when balancing indices. If the cache is
small, or if the disk I/O is slow, then performance WILL suffer.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: September 16-18: See our web site for details!

Ralf Rochow wrote: