Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Tablespace best practices

Re: Tablespace best practices

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Sun, 26 Dec 2004 20:37:21 -0800
Message-ID: <41cf9070$1_4@127.0.0.1>


Comments in-line.

Access wrote:

> Hi,
>
> I was wondering what the "best practices" are regarding tablespace creation
> :
> - separate tablespaces for data/indexes ?

Waste of effort accomplishing nothing.

> - separate tablespace for each schema ?

Depends. Separate by application yes but by schema probably not.

> - large/medium/small objects in separate tablespaces ?

A good practice but not just because of the size.

> - locally managed with auto or manual segment space management ?

Absolutely unless you have something specific about your situation where you can demonstrate, by lab testing, that it is negatively impacting your application.

> Just wanted to hear some pro/contra's ...

I suggest separating domain tables, lookups, into read-only tablespaces. Back them up once or twice and then forget them until a change is made.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)
Received on Sun Dec 26 2004 - 22:37:21 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US