Hi!

It looks like your indexes are quite large. In addition, when table contains a lot of deleted records or memo fields content edited often, you need to use PACK command.

Another reason - no indexes or table have collation sequense set. Both prevent Rushmore optimization causing both query and update slow.

Remove collation sequense, remove all indexes and create them again. Pack table to pack memo fields and remove deleted records to make index file smaller.

Finally, do not use filtered indexes, they're never used for optimization. For example, indexes like
INDEX ON aaa tag aaa for !deleted()
were quite popular some time ago. Remove filters from indexes that you require for optimization.

HTH.

>Hi,
> I am using local view to update records in a module. The view will query about 5000 records which contains 4 fields (about 100 bytes per record).
> I am using view designer to set the view's property. The settings are as the following:
>
>SQL Generated: SELECT f1,f2,f3,f4 from mytable where f1 = .f. order by f1 asc
>Fields name in update criteria: f1 (updatable), f2 (key field), f3,f4
>SQL WHERE cluase include: Key fiedls only
>Update using: SQL Update
>Send SQL updates: TRUE (checked)
>
>The query takes 6 seconds to load data. It is ok since i am using 10BASET LAN. However, this view also take 6-8 seconds to update records. The view is buffered using 5-TABLE BUFFERING and updated using TABLEUPDATE(2, .F.).
>
>Any ideas for the reason of slow update?
>
>Thank you