Re: Large table extents

Yes to question 1. Yet, if you have an index and set up query correctly to use index it will use it. But once a table becomes highly fragmentted either due to delete or insertions it is a good idea to unload and reload the table. Or if you have enough space within the dbspace just alter the index to cluster (this will also unfrag the table). ------------------------------------------------------------------------- Cheryl Kendricks Internet: cherylk@spamis.jcdc.doleta.gov OR cherylk@prod1.jcdc.doleta.gov OR kendric@gwysmtp.jcdc.doleta.gov DTSI, Inc. Voice: 1-800-598-5008 Database Adminstrator - DOL Job Corps San Marcos, Texas ------------------------------------------------------------------------ On Wed, 13 Mar 1996, Craig Ostrom wrote: > Can anyone answer the following questions? > > 1. When rows are deleted from a table, are the remaining rows left > scattered over the table extent? > > 2. When these remaining rows are queried, given that 1. is true, does > Informix sequentially scan through the whole table extent including > empty pages? > > I ask this because that is what seems to be happening and if it is, then > we need a way to defragment the table extent. > > I would think that this means unloading and re-loading the table. > > Is there anything else that can be done to stop this kind of fragmentation? > > Thanks for your time. > > Stanton Attree. >