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: Oracle's Myth: keep tables and indexes in separate tablespaces

Re: Oracle's Myth: keep tables and indexes in separate tablespaces

From: dario diano <dariodia_at_yahoo.com>
Date: 9 Oct 2003 07:59:56 -0700
Message-ID: <1855b474.0310090659.319ce60b@posting.google.com>


pardon me...
I'm just movinng into the fashinating world of Oracle DB, Can you explain me How creating a table and an index on this table on the same tablespaces impact the performances... Isn't it about concurrent phisical disk access(tablespaces are on one phisical disk)????

Thanks in advance.

"Snid" <snid_at_snider.sno> wrote in message news:<bm2qs6$o1$1_at_bunyip.cc.uq.edu.au>...
> It's interesting to see where the idea that it is good to keep tables and
> indexes in separate tablespaces comes from. I know that this topic has been
> done to death, but I've just been reading through Oracles own teaching guide
> titled:
>
> Enterprise DBA Part 1A: Architecture and Administration
> Volumn 1 . Student Guide
> which was printed in August 1999
>
> I see that in Lesson 11, Managing Tables, it gives the first guideline for
> creating tables as,
>
> "Place tables in a separate tablespace - not in the tablespace that has
> rollback segments, temporary segments, and indexes."
>
> So I guess I can see why lots of people think that it's best to separate
> indexes from tables. It doesn't mention that you should only separate them
> for administration purposes mainly.
Received on Thu Oct 09 2003 - 09:59:56 CDT

Original text of this message

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