Message-Id: <24738.322731@fatcity.com> From: Jacques Kilchoer Date: Fri, 21 Mar 2003 10:59:38 -0800 Subject: RE: RE: Locally Managed Tablespaces This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2EFDC.054CFB90 Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: rgaffuri@cox.net [mailto:rgaffuri@cox.net] > > thanks in case I happen to work on a 7.3 database.... > > what kind of pctincrease should I set? What about the other > settings? Just curious. The current thinking is that uniform extents are a good thing. So in 7.3, try and "manually" enforce uniform extents: initial = next for all clusters/tables/indexes in the same tablespace pctincrease=0 for all objects These should of course be the settings for the DEFAULT STORAGE clause on the create tablespace. Then to create a cluster/table/index you can (should?) use tablespace defaults and skip the storage parameter on the CREATE cluster/table/index statement. My personal opinion: always use maxextents unlimited but put your object in a tablespace where the values of INITIAL and NEXT will prevent the object from having more than 1000 extents. Autoextend datafiles: my personal opinion is don't use those, because you should have an idea of how and when your database is going to grow, and if you need more space it's nice to be aware of it. Of course this means the risk of failure when a datafile is full, but the same thing can happen with autoextend when the disk gets full. ------_=_NextPart_001_01C2EFDC.054CFB90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: RE: Locally Managed Tablespaces

> -----Original Message-----
> From: rgaffuri@cox.net [mailto:rgaffuri@cox.net]
>
> thanks in case I happen to work on a 7.3 = database....
>
> what kind of pctincrease should I set? What = about the other
> settings? Just curious.

The current thinking is that uniform extents are a = good thing.
So in 7.3, try and "manually" enforce = uniform extents:
initial =3D next for all clusters/tables/indexes in = the same tablespace
pctincrease=3D0 for all objects
These should of course be the settings for the = DEFAULT STORAGE clause on the create tablespace. Then to create a = cluster/table/index you can (should?) use tablespace defaults and skip = the storage parameter on the CREATE cluster/table/index = statement.

My personal opinion: always use maxextents unlimited = but put your object in a tablespace where the values of INITIAL and = NEXT will prevent the object from having more than 1000 = extents.

Autoextend datafiles: my personal opinion is don't = use those, because you should have an idea of how and when your = database is going to grow, and if you need more space it's nice to be = aware of it. Of course this means the risk of failure when a datafile = is full, but the same thing can happen with autoextend when the disk =