RE: Large in memory DW table

Rob,  

Out of curiosity some back to basics question.  

1. What is your current performance bottleneck and would having the table in SGA remove that bottleneck
2. Why does this table need to be in memory
3. Can you use indexes and partitioning effectively to defer the table row access until later? Indexes tend to be more compact and consequently better at being cached, not to mention the join optimization you may get
4. Can PQ be an alternative

My preference and experience, in general, is to articulate the performance problem and goals in business terms. There is an inherent danger to expressing the performance problem in terms of a solution you may choose (caching the table). If the requirements necessitate that, wouldn't it then be perhaps better to look at the products such as Oracle Times Ten rather than shoe horn it into Oracle RDBMS?  

-Krish

--
http://www.freelists.org/webpage/oracle-l