Printable View
If you are not deleting data then PCTUSED does not matter, but just set it to 99.
If you set the table to nologging then you should preserve your source data until the database has been backed up.
Partitioning would be useful for dropping old data easily or for enhancing performance if users will commonly use a particular set of columns to filter their result sets.
When you said "sql loader" a bell went off.
Would the option to use oracle's external table feature be an alternative?
But, I think external table is not supported in Oacle 8.1.7.
Some commenst from me aslo
1) Partitioning is a good idea. Sooner or later you'll need to do someting with the data for particular mont and that will be a pain without partitioning.You could even consider placing a partition or several partitions in separate tablespace and making it read only after the load. This would help with the backup lately and also with unpluging/pluging data into the database using the new 10g R2 features
2) Dave, why you do not like ASSM? Some bad experience or..?
3) OracleDoc, I do not see a huge benefit in the external tables compared to the loader. It could operate a bit easyer but since the scripts are created, it should not matter so much
ASSM prevents the stored rows from being clustered by value -- they get scattered around. In this case there is a single loading process so there is no contention to avoid on the insert (one of the primary purposes of ASSM) and you just want the data to be packed as tightly as possible. MSSM, PCTFREE 0, compression, and sorted data is the way to go.Quote:
Originally Posted by Bore
Sorry for coming in...
REDO generation.Quote:
3) OracleDoc, I do not see a huge benefit in the external tables compared to the loader. It could operate a bit easyer but since the scripts are created, it should not matter so much
Cheers.
Carlos.
Seems I do not understand something. So loading by ext tables does not generates redo and the loader does?
The loader also has direct path loading if that's in question