Re: naming convention tablespaces

Here is the convention I'm using, all LMT using extent sizes recommended by Oracle whitepaper #711

<schema>_appname##_sdat  data segments, 128K extents
<schema>_appname##_sidx  index segments, 128K extents
<schema>_appname##_mdat  data segments, 4MB extents
<schema>_appname##_midx  index segments, 4MB extents
<schema>_appname##_ldat  data segments, 128MB extents
<schema>_appname##_lidx  index segments, 128MB extents

<schema> is optional, but used when there are multiple schemas using the same application (or product) within the same database instance. ## is optional, but used when more tablespaces are needed (01, 02, 03,etc) for that extent size.

Suzy

nlzanen1_at_ey.nl wrote:
>
> Hi All,
>
> I am in the proces of putting together a reorg plan for one of my
> databases.
> We now have 1(one) data tablespace with a mixture of extent sizes
> (generally too small).
> This tablespace is called "<application>data".
>
> I want to have say 5 tablespaces with different extent sizes and don't use
> the storage clauses for the individual tables but rather lett the
> tablespace decide the storage clause a table will have.
> What (if any) is the standard for naming the tablespaces??
>
> I was thinking "<application>data_S" "<application>data_M" etc. etc.
>
> Jack
>
> ===================================================================
> De informatie verzonden met dit E-mail bericht is uitsluitend bestemd voor
> de geadresseerde. Gebruik van deze informatie door anderen dan de
> geadresseerde is verboden. Openbaarmaking, vermenigvuldiging, verspreiding
> en/of verstrekking van deze informatie aan derden is niet toegestaan.
> Ernst & Young staat niet in voor de juiste en volledige overbrenging van de
> inhoud van een verzonden E-mail, noch voor tijdige ontvangst daarvan.
> ===================================================================
> The information contained in this communication is confidential and may be
> legally privileged. It is intended solely for the use of the individual or
> entity to whom it is addressed and others authorised to receive it. If you
> are not the intended recipient you are hereby notified that any disclosure,
> copying, distribution or taking any action in reliance on the contents of
> this information is strictly prohibited and may be unlawful. Ernst &
> Young is neither liable for the proper and complete transmission of the
> information contained in this communication nor for any delay in its
> receipt.
> ===================================================================
>
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> --
> Author:
> INET: nlzanen1_at_ey.nl
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
Received on Wed Nov 01 2000 - 14:03:08 CST