Re: default index tablespace?

<wutang_warrior_at_my-deja.com> wrote in message news:92g0hm$mbn$1_at_nnrp1.deja.com...
> So wouldn't it be a good idea to have the ability to assign a default
> index tablespace to users?
>

Well, if we're talking good ideas, it would be a good idea if Oracle would install itself in *just* the right location without furthur hassle or intervention; it would be a good idea if it would read the mind of the users, instead of them having to type stuff in; it would be a good idea if Oracle would respond to the rapid eye movements of the DBA whilst s/he remains snugly in bed of a morning.... and I can't wait for the "create or replace a nice cup of tea and breakfast in bed and would you mind doing the ironing? package body".

I think, on the other hand, that perhaps there ought to be a minimum level of competence and involvement on the part of the DBA that the software could expect. It's already helping prevent inadvertent segment creation in SYSTEM tablespace with the 'default tablespace' command... how much more help do you want or need?

Presumably, going down the path you suggest, we should also have to have a 'default index cluster tablespace', a 'default index-organized table tablespace', a 'default hash cluster tablespace', a 'default rollback segment tablespace' ...and on and on and on. At this rate, it will take 15 minutes to create each User account.

Regards
HJR
>
>
> In article <3a4af958_at_news.iprimus.com.au>,
> "Howard J. Rogers" <howardjr_at_www.com> wrote:
> > Comments below.
> >
> > <wutang_warrior_at_my-deja.com> wrote in message
> > news:92eclj$fmn$1_at_nnrp1.deja.com...
> > > Must I specify the tablespace for my indexes with all my DDL?
> > > isn't there a default_index_tablespace for dba_users?
> > >
> >
> > No. You set a 'default tablespace' for all Users (including SYS and
> > SYSTEM). That's the tablespace in which segments will be stored
 unless the
> > relevant "create" statement explicitly states otherwise. In this
 regard,
> > Oracle makes no distinction between table segments and index segments.
> > They're both segments, and both would end up in the same default
 tablespace.
> >
> > However, it's just sloppy practice not to explicitly state the
 required
> > tablespace at create time, so it shouldn't be an issue.
> >
> > > What about the different names given to the Index tablespace between
> > > Oracle versions?
> >
> > Who cares? Oracle certainly doesn't. ALL tablespaces, bar SYSTEM,
 have
> > names which are at the whim and mercy of the relevant DBA. You can
 call
> > your data tablespace "DATA", "DATA01", "USERS" or "HAPPYNEWYEAR" -
 Oracle
> > won't mind one way or another. And the same goes for the Index
 tablespace.
> > So the names different DBAs use has precisely zilch to do with the
 version
> > you are using.
> >
> > >can I just change it to whatever I like when creating
> > > my DB or do catalog.sql, catproc.sql, etc... rely on it?
> >
> > See above. No they don't. Catalog builds the data dictionary views -
 it's
> > only concerned with finding a tablespace called SYSTEM. Catproc is
> > concerned with enabling PL/SQL functionality and building certain key
> > packages -which also reside in SYSTEM.
> >
> > >I suppose
> > > their indexes just sit in the SYSTEM tablespace....
> > >
> >
> > They certainly do.
> >
> > HJR
> >
> > >
> > >
> > >
> > > Sent via Deja.com
> > > http://www.deja.com/
> >
> >
>
>
> Sent via Deja.com
> http://www.deja.com/
Received on Thu Dec 28 2000 - 15:29:37 CST