I expect the update of .cdx to be at the same time that the .dbf is done.
223 meg is a tiny index size and reducing it down to 1/4 probably didn't make anything faster, did it? Now an index of 20 gig that would probably be noticed if you brought it in line to only 5 gig.
On Wed, Jan 24, 2018 at 2:11 PM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
Thanks. In this app, they indexed EVERY field, and the table in question had a CDX size of 233 MB before I pruned it. Now it's down to 56 MB.
On 2018-01-24 14:35, Alan Bourke wrote:
Only the indexes that involve a 'touched' field. And even then it's just a small update.
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
On Wed, 24 Jan 2018, at 6:29 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Question for you legends of the Fox (data):
Say Table1 has "X" number of indexes. Program code does something like the following:
IF Condition1 THEN REPLACE Field1 with SomeValue in Table1 ENDIF
IF Condition2 THEN REPLACE Field48 with Datetime() in Table1 ENDIF
Are each of the "X" indexes updated for each replace, even if those indexes do not include any reference to Field1 or Field48, or only indexes that are affected by the data value change?
I understand that ADDing and DELETEing records updated all indexes; I would think the UPDATEs--regardless of what fields updated--would cause index updates for every indexed field on every update as well.
tia, --Michael
[excessive quoting removed by server]