RE: naming convention tablespaces

From: Thomas Jeff <ThomasJe_at_tce.com>
Date: Wed, 1 Nov 2000 12:57:40 -0500
Message-Id: <10667.120827@fatcity.com>

Jack,

We do something like that.... this is from our standards:

Tablespace names should clearly indicate the schema, object type, and object sizing with respect to the uniform extent size.

The following syntax should be used:

	Data:		{APPID}_{SIZE}_DT{NN} 
	Index:	{APPID}_{SIZE}_IX{NN}

Where:  
       {APPID} is the schema name,
       {SIZE} is a two-letter code (SM for SMALL, LG for LARGE, etc)
	        identifying the size attribute of the tablespace and
              {NN} is a sequential number starting with 01.

The following guidelines defines the relationship between uniform extent sizes, object sizes, and the tablespaces:

Tables:

Size Attribute 		Extent Size		Object Size  
X-Small  {XS}		64K			Smaller then 32M
Small	   {SM}		128K			Between 32M and 64M
Medium   {MD}		4M			Between 64M and 2G
Large    {LG}		128M			Between 2G and 64G
X-Large  {XL}		256M			Between 64G and 125G
XX-Large (2X)		512M			Greater then 125G
	
Indexes:
Size Attribute 		Extent Size		Object Size
Small    {SM}		64K 			Smaller then 32M
Medium   {MD}		2M			Between 32M and 1G
Large    {LG}		64M			Between 1G and 32G
X-Large  {XL}		128M			Between 32G and 64G
XX-Large (2X)           256M              Greater then 64G

Hope this helps.

Jeff T.
thomasje_at_tce.com

-----Original Message-----
From: nlzanen1_at_ey.nl [mailto:nlzanen1_at_ey.nl] Sent: Wednesday, November 01, 2000 9:00 AM To: Multiple recipients of list ORACLE-L Subject: naming convention tablespaces

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

Received on Wed Nov 01 2000 - 11:57:40 CST