Incremental index updates

[Ruslan Zasukhin]

On 4/9/12 1:30 PM, "Beatrix Willius" <bwillius at gmx.de> wrote:

Hi Beatrix,

> have been testing V5 here for a bit. Report to follow separately. One general
> issue: I have changed from indexing during adding records to indexing after
> adding records. This has one drawback. When only a few records are added the
> complete database is indexed.

I think not db, but table.

> With this the indexing may take much longer than
> adding the records. Is there any possibility to get some sort of incremental
> index?

I think more simple for you add logic that you disable indexes only if you
going insert m records and
            m > 10% of Table.PhysicalRecordCount


We self using such "rule of thumb" in engine ...


=============
Incremental indexing or batch adding to index is another story ...
And It should use another flag. Not disable indexing, but DelayIndexing.

This is complex thing, because many dependencies.
Locally in single thread this will delay anyway later.

In vserver environment, such indexing can be made may be later IF other
users do not conflict immediately ...

Not easy ...


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]