Re: Newbie question about Tablespaces (and database creation).

Greg,

Setting the default storage is a good idea, although not absolutely necessary. I like to keep it small so that users are forced to think about storage for large tables. Also, set default pctincrease to 1 for the tablespace, so that SMON will coalesce free space in it.

For tables, it is certainly good practice to always use a storage clause when creating tables and indexes. (IMMHO, this separates better developers from poorer ones.) Extent sizes should (according to current wisdom) come from a pool of sizes that are increments of each other, i.e., 512k, 1M, 2M, 10M, 50M., or 1M, 2M, 4M, 8M, 16M, 32M. Pick a size for initial and next (usually the same size) so that when the table grows it won't be using hundreds of extents. My experience is that under 40 extents should be ok performance wise. Also, set pctincrease to 0 for your tables.

HTH, Yosi

Greg Akins wrote:

> Thanks, just for clarity
>
> Should it be:
>
> CREATE TABLESPACE APPL_DATA DATAFILE 'APPL_DATA'
> SIZE 100M AUTOEXTEND ON NEXT 10M MAXSIZE 1000M
> DEFAULT STORAGE
> ( INITIAL 100M NEXT 10M
> MINEXTENTS 1
> MAXEXTENTS 10 PCTINCREASE 1 )
> MINIMUM EXTENT 10M;
>
> or just
>
> CREATE TABLESPACE APPL_DATA DATAFILE 'APPL_DATA'
> SIZE 100M AUTOEXTEND ON NEXT 10M MAXSIZE 1000M ;
>
> Then when I create the table do I specify a real size for
> initial (how should I determine extent size for the table)?
>
> -greg
>
> **** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ****
Received on Fri Jul 16 1999 - 11:55:03 CDT