RE: TableSpace Storage Parameters?

Generally, it's good to create an initial extent that can hold all of the data in a given table. This is easier to do at the table level than at the tablespace level, but if you create tablespaces which contain tables with common size and growth patterns, you can assign an initial extent which should hold the all the data for the majority of tables within that tablespace. This will take some research on your part to determine what the average total sizes are for your tables. The NEXT extent should be sized at something close to how much you feel these tables might grow within say a few months. The idea being that you don't want to waste a lot of space with huge next extents, but at the same time you don't want to end up with a lot of additional extents if you make NEXT too small. Also, remember that these values will only come into play if there are no INITIAL and NEXT sizes specified in the CREATE TABLE statements for the tablespace.

Hope this helps.

> -----Original Message-----
> From: Gin, Jeannine (EXCHANGE:QUAL:7S02)
> [SMTP:jgin_at_americasm01.nt.com]
> Posted At: Wednesday, February 03, 1999 3:01 PM
> Posted To: comp.databases.oracle.server
> Conversation: TableSpace Storage Parameters?
> Subject: TableSpace Storage Parameters?
>
> How does one choose an appropriate initial and next extent sizes of a
> tablespace?
>
> For example:
>
> create tablespace mytablespace
> datafile '/disk9/isd/data/mytablespace.dbf' size 100M
> default storage (initial ??M next ??M pctincrease 0);
>
>
> Thanks in advance,
>
> Jeannine
Received on Thu Feb 04 1999 - 08:48:02 CST