| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.misc -> Re: Tablespace and tables question
IMHO, multiple tablespaces, each containing one or several tables, is a good idea if you have enough disk drives to put each tablespace on its own drive, and ideally, under different disk controllers, to improve performance. However, nowadays you can use RAID in its various incarnations to the same end.
Another reason to separate tables in several tablespaces is for space management, i.e. segregate tables with different fragmentation characteristics in different tablespaces. This way you will avoid the need for an entire database reorg and reorg only the heavily fragmented tables/tablespaces (clean and fast).
The usual recommendation is to store different segments (data vs. index vs. rollback vs. temporary) in separate tablespaces.
In your situation, I would store the dynamic tables in one tablespace and the 2-3 static tables in a different tablespace. After you load the data in the static tables, you could make that tablespace a READ ONLY tablespace (which you could put even on a CD-ROM and will not need to backup). As a possible further refinement, you could use a third tablespace to store the dynamic tables which experience heavy insert/update/delete activity.
Hope this helps.
Michael Serbanescu
 |
 |