By "no longer needed" I was referring to Chip's suggestion of reindexing with SQL. Prior to v15R-release indexes were built in creation order, which made horrible use of the cache. Now it goes in table order which makes it MUCH faster on a large data file.
I think I understand the problem you're describing - it's not something I've experienced. The cache should definitely be used once it gets to the indexing part. I don't think cache is used in the initial rebuilding part. > On Jul 26, 2018, at 12:35 PM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > What do you mean by "no longer needed in 16"? There is a Get table > fragmentation command that might be saying compaction is needed. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
