Thanks, this what I'm finding too, and it's really bad news. Our database needs to be available 24/7 due to being in the international market. When disabling the index on the SO, then enabling and updating, the update causes locks the file - not good as our company runs off the SO file. Locking that file means we have scheduled "downtime" where we do no make money, the Powers That Be won't have any of that.
Boydell, Stuart wrote: > > I have found that deletes are the hardest on index updating, slower than > inserts. If you can, I'd specifically disable the delete from the SO file > to see what change that makes. > Cheers > Stuart > > -----Original Message----- > Basically what happens with the code that does the archiving is it reads > the > SO record, does some quick checks to make sure we can move it, then writes > the record to SOH, then deletes the SO. > > There are 7 indexes on the SO file and 5 on the SOH. > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users > > -- View this message in context: http://old.nabble.com/Slow-READ-WRITE-with-indexes-tp29653705p29676533.html Sent from the U2 - Users mailing list archive at Nabble.com. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
