Re: Growth planning

Frank Calfo wrote:

> When planning for the growth of the database is it generally better to
> start with small initial and next extents to reduce free space and add
> datafiles as you run out of room
> or is it better to start with large initial and next extents to minimize
> the number of total extents and additional datafiles needed later?

Hi Frank,
try to calculate the initial sizes of your db-objects ( clusters, tables & indixes ).
Afterwards you should estimate how much the objects would be increased during the next half year / 2 Years.
If you've static tables just use the amount of space they'll need as initial extent.
For growing tables you should calculate the initial extents as large to keep initial data volume plus data volume of the next 6 months. Usually you can't say how the data is growing on each table exactly. By sizing the initial extents in that manner you avoid fragmentation and get quicker guery results.
Another hint: keep enough free space in your tablespaces to make extent-allocation possible.

Greetings,
Tobias Hitzfeld Received on Fri Oct 01 1999 - 06:08:40 CDT