This would imply that the code was looping over the recordset and
updating the Verity collection one record at a time.  Inevitably this
leads to massive fragmentation of the Verity index and consequentially
VERY slow performance until you optimise the collection.


Well, that wasn't really an issue.  I had to keep the collection fairly
fresh, which was a pain.

As for optimising, you can set up a single job to automatically optimise
all the collections on a single server:


Back in the bad old days of wimpy servers, this took too long.  So I had no
choice but to separate the optimizations.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to