Re: Fragmenting tables/indexes

Are you sure that your queries are _actually_ using the fragments to eliminate data from the searches? We had a similar situation where data was fragmented by dates. But when we ran certain queries, the optimizer ignored the fragmentation scheme altogether, performing searches of all fragments when it should have been able to eliminate subsets of data. Cosmo Kate_Tomchik@HomeDepot.COM wrote: > Hi. We have a system that we have fragmented based on Date so that > when we > purge our system on a daily basis we simply drop the oldest fragment. > This > part works > superbly, but retrieval of records seems to be unneccesarily slow. I > believe that > what we need is a separate dbspace for the indexes, but other DBAs > feel > that this > will cause more problems because the indexes will have to be rebuilt > to > drop the > data fragment. Am I wrong to assume that the index pages will work > like > data pages > and simply "mark" the rows that are no longer used, and reuse these > spaces > as > needed for the next day's data? > > FYI the table has more than one index, and only one is organized with > the > date > field first. -- * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ADDRESS ALTERED TO FOIL SPAMMERS: Remove "*NO-SPAM*" to reply. Cosmo Lee Multi-User Computer Systems Brooklyn, NY "JUST SAY 'NO' TO SPAM" * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *