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

Generally speaking your idea has some sence. Oracle separate tablespaces design looks as naive as partitioning NT hard drive into C: and D: and placing all system files into C. As if it provides better security and space management. At my work IT stubbornly continuing this stupid practice of arbitrarily dividing one disc into 2 smaller parts. As a result, my small C: partition is easily running out of space, so that I have headaches all this unnecessary space management. Although, if you are a DBA, space management shouldn't bother you too much.

Practical comment. System tablespace has some separate logic that you might be not aware of. For example, until recently skip-scan index scans were disabled on system tablespace. God knows how many other if conditions are in oracle code so that you'll get *different* functionality on system tablespace. That warning should be enough to discourage you of the experiment;-)

"Vinu Neelakandhan" <vinu_neelakandhan_at_hp.com> wrote in message news:bdree0$48n$1_at_ctss92.sgp.hp.com...
> Hello all :
>
> Can someone tell me the disadvantages (or advantages, if any) of creating
> user tables within the default SYSTEM tablespace?
>
> I understand that it is ideal to have user's own tablespaces (rather than
> creating within SYSTEM, where the DD etc are being kept), but would like
to
> know the actual disadvantages of doing within SYSTEM. Does it impact the
> performance? Or, does it impact anything else?
>
> Thanks in advance,
> Vinu
>
>
Received on Tue Jul 01 2003 - 13:45:14 CDT