Extent sizes

Hello Tuners, I would like to have a better feeling about the performance impact of the definition of extent sizes (first and next) for tables. In our production database ( Online 5.01 ) we have already tables with about 50 extents. tbcheck already gives a warning at 8 extents. Are there any experiences or guidelines of configuring the first and next extent size the best way? How big can the performance degradation be if configured in a bad way ? ( access is n times slower ? Which n ) Is it possible to change these for the system tables as well? These tables were the first ones exceeding the warning level of 8 extents! Thanks in advance for any hints. Achim -- ========================================================================== / Achim Reiners Software Engineering \\ | /M/A/I Deutschland GmbH | | Softwarezentrum Koeln Phone: +49 221 956400-40 | | Mathias-Brueggen-Str. 85 Fax: +49 221 956400-69 | \\ 50829 Koeln E-Mail: ar@mai.de / \\_________________________________________________________________________/