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

Home -> Community -> Usenet -> c.d.o.misc -> Re: Advantages/disadvantages of having tables within 'SYSTEM' TS

Re: Advantages/disadvantages of having tables within 'SYSTEM' TS

From: Mikito Harakiri <mikharakiri_at_yahoo.com>
Date: 8 Jul 2003 09:13:58 -0700
Message-ID: <bdf69bdf.0307080813.22b33f29@posting.google.com>


"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in message news:<3f0495c4$0$10630$cc9e4d1f_at_news.dial.pipex.com>...
> Hmm. Why would I issue
>
> alter user COGNOS quota zero on DATA quota 2048g on REPORTING;
> and
> alter user SAP quota unlimited on DATA quota zero on REPORTING;
>
> ?

Your example sounds like security and access control, not about storage management. You want to allow user SAP Reporting functionality only? Grant appropriate permissions, then.

For one thing, how did you calculate 2048g number? If it is always "zero" and "unlimited", then it's access control. And the question remains if yet another partitioning of oracle objects (tablespaces) serves any useful purpose. Received on Tue Jul 08 2003 - 11:13:58 CDT

Original text of this message

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