NOLOGGING Question - System tablespace

I have a question. Oracle 8 has a feature called 'NOLOGGING' that will prevent redo being generated for updates, inserts or deletes at the object and tablespace level. We have a data warehouse where due to the fact we can parallel load about 8 million rows in about 20 minutes, we don't do backup's on it. So for any adhoc dml that is done we don't care about any redo being done, much less any rollbackup info for the same.

The question is :

Is it recommended to apply 'NOLOGGING' to ALL tablespaces ? I mean I know that no redo is generated for temporary segments - but what about the SYSTEM tablespace, SYSTEM rollback and our other rollback segments. Can any performance be gained from applying 'NOLOGGING' to these ? More to the point is it a No No, and if so why ?

Thanks

--



============================================================

Pieter Viljoen
ABSA Group                         Tel.(local) 011 350 6452
P.O. Box 422                           (int.)  +27113506452
CRESTA                             Fax.(local) 011 350 6228
2118                                   (int.)  +27113506228
Republic of South Africa


============================================================