Re: tablespace design for datawarehouse

Posted by ErmanArslansOracleBlog on Oct 26, 2018; 8:31am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/tablespace-design-for-datawarehouse-tp6873p6875.html

It is a matter of choice, but as I already mention;  you may have multiple tablespaces  and you may decide "which tables should go to which tablespaces" according to their sizes.

For ex: all the small objects should reside in a tablespace, and this tablespace should only be used by the small objects..

This will prevent the fragmentation..

But, you may also use multiple tablespaces and you may implement a tablespace model by taking consideration of the following rules.. (like we have EBS 12.2)

-- This kind of a model is prepared by taking consideration of size,life span,access methods and locking granularity..

Object Type                            Tablespace
AQ Tables                                         AQ
IOTs (Index Organized Tables) Transaction_Tables
Materialized Views                     Summary
Materialized View Logs             Summary
All other Indexes            Same Tablespace type as the table
Domain Indexes                        Transaction_Indexes
Indexes on Transaction Tables Transaction_Indexes

So, in these mode you are considering, object type + access methods..

so you choose one of these 2..