dbimport and extents

Dr Richard Spitz (spitz@ana.med.uni-muenchen.de) posted: > Bill Ennis (ennis@ssd.comm.mot.com) wrote: > : Warning: If you are using Online you will lose the dbspace/extent > : information ;( However, it does fit all tables into one extent ;)). > > How can Online fit all tables into one extent? AFAIK, dbimport > uses the default extent size of 16k, so large tables will get > split into many little pieces, and performance will degrade serious- > ly if the number of extents exceeds 8 for a table. For what its worth... We have had some experience with extents and Online 5. Research showed us that extents are non-contiguous chunks of space. This means that if you load data to fill 10 16k extents and you load this info in such a way that Informix will place all 10 extents together (like a dbload when nobody else is using the database), Informix will count the contiguous space as one single extent. This can be a big problem with tables like the sysproc* tables. Informix does not give you much control on extent sizes of system tables, but a reload of the database does help to clean things up a bit. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Miguel A. Caldera ! Antares Development Corp. ! Phone (210) 490-9626 mac@antares-dev.com ! 1000 Central Pkwy North ! Fax (210) 490-0874 73564,2200 Compuserve ! San Antonio, TX 78232 USA ! #include <std_disclaim.h> ----------------------------------------------------------------------------- =-> I haven't lost my mind, I know exactly where I left it!!! <-=