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 and users

Re: TableSpace and users

From: Matt Surico <surico_at_buoy.com>
Date: Wed, 29 Jul 1998 22:55:00 -0400
Message-ID: <35BFE083.C3BBA607@buoy.com>


Danielle Fortes wrote:

> I´m just starting with Oracle so ... sometimes i´m going making stupid
>
> questions! :)
>

    The only stupid question is the one you don't ask...you gotta start somewhere, right? :-)

> Well ... I was thinking to use Oracle´s tablespaces to separate
> database
> objetcs from several different applications like Human resources,
> Payroll
> and others ? I know the advantages but could someone tell me about the
>
> disadvantages to use this resource ? We develop products so I beleive
> that
> using tablespace I can improve distributions too.
>

    I can't really think of any *disadvantages* other than the fact that if you go nuts with creating tablespaces, remember that a tablespace is owned by a datafile, and if you create too many datafiles, you might run into problems if you haven't set MAX_DATA_FILES in your init.ora high enough. Other than that, as long as you stay organized and grant the right resources on the right tablespaces to the right people you should be ok.

> The other question is:
>
> Are there any problems to create some objetcs of database using SYSTEM
> or
> SCOTT user´s ?
>

    You should be careful if you create objects as SYSTEM, being especially careful *not* to create any of your own objects in the SYSTEM tablespace. If you have your own objects owned by SYSTEM, who else needs access to them? Do you really want to allow users access to the SYSTEM schema? And definitely avoid filling up the SYSTEM tablespace. What I usually do is only let SYS create objects in SYSTEM tablespace (as is required for data dictionary) and force the SYSTEM user to use a separate tablespace you create yourself (like TOOLS).

    Nothing inherently wrong with using SCOTT; just make sure that for security sake you change the default password of SCOTT from TIGER to something else. You'll probably find as you gain confidence using Oracle schemas that you'll want to create your own and remove the SCOTT one altogether, creating one that is more meaningful to you, like HR_USER or whatever.

    Good luck and hope this helps!

Matt

> Thanks in advanced!
>
> Danielle Fortes
> fortes_at_metalink.com.br
> Remix Tecnologia Ltda
> Brazil

--
Matt Surico
Oracle Certified Database Administrator surico_at_buoy.com
http://www.buoy.com/~surico Received on Wed Jul 29 1998 - 21:55:00 CDT

Original text of this message

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