RE: Extents: Reality and Myth

Sorry, you're right Doug. I was smoking crack the day I wrote that. :) -Scott > -----Original Message----- > From: owner-informix-list@iiug.org > [mailto:owner-informix-list@iiug.org]On Behalf Of Doug Agnew > Sent: Friday, March 17, 2000 11:07 AM > To: informix-list@iiug.org > Subject: Re: Extents: Reality and Myth > > > Scott, > > I don't think that interlaced indexes form another extent..... > > Doug > "Scott Huppert" <shupp@cfer.com> wrote in message > news:8atr2j$olk$1@news.xmission.com... > > > > >> 4. If a dbspace is dedicated to a single table, that table will have > one > > >> and only extent regardless of what extent size and next > extent size is > > >> set to: ___ True ___ False. > > >Again, it depends. As long as the dbspace takes up only one > chunk, then > > >the answer would be true. If the dbspace spans chunks, it would be > > >false. And it also depends on what freespace was left after the tables > > >originally in the dbspace were moved; each of those freespaces would be > > >an extent. > > > > Unless the indexes are detached, you will have multiple extents even > within > > the same chunk assuming that the amount of data grew over time. > The data > > will all be in the same chunk, but it will be interlaced with the data > > causing multiple extents. (If the indexes were created _after_ the data > was > > loaded, the extent could expand to adjacent disk and become one large > > extent.) > > > > -Scott > > ___________________________________________________ > > Scott Huppert, Database Administrator > > Sonata Informix NextGen Systems > > Global Crossing Conferencing > > 12110 North Pecos St. > > Westminster, CO 80234 > > Voice: 303.633.3917 > > Fax: 303.633.3001 > > E-Mail: shupp@cfer.com > > > > > > >