Make sure you do some testing first. Under UniData I found that disabling the index made things much worse. It created a log file and put a copy of each record (appears to be the entire record - and not "optimized" for just the required index info) into it. The bad part was we were building a reporting cube so each record was written many times - which were all in the log file. This created a HUGE log file and was actually slower than leaving the index disabled. Plus it had to apply each of these records once we re-enabled/updated the index.
It was actually much faster to remove the index, build the file, and then rebuild the index. Maybe it's better now - or maybe it just wasn't designed for what we were doing.... Hth Colin Alfke Calgary, Canada -----Original Message----- From: Ryan M I'm trying this now, thanks. Larry Hiscock wrote: > > Are any of your indices based on virtual fields? I haven't worked with UV > in a while, but UD has the DISABLE.INDEX, ENABLE.INDEX and UPDATE.INDEX > commands. If UV also has them, you could disable the indexes prior to the > archival and re-enable and update them at the end. I'm not sure if it > would > be any faster, but certainly worth an attempt. > > Larry Hiscock > Western Computer Services _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
