Hello folks,
I had a couple of questions on setting up tablespaces for our DW (single instance 10gR2 EE).

1. We'll have, say, 10 dimension tables (some small, some rather large - maybe into millions of long rows). Is there any performance benefit in creating multiple tablespaces for these dimension tables? In other words, what do we lose if we create all the dimensions on a single, bigfile tablespace? Assume the latest storage with proper RAID and I/O bandwidth. If we should be using multiple tablespaces, what's the recommendation - 1 tablespace per dimension table? Some other ratio?

2. I keep seeing discussions on setting extents for fact table tablespaces to be uniform instead of auto. What's the benefit there? I'm wondering if it's that big of a performance gain (can't see one via my tests so far).

3. OK, not a tablespace question, but ... what do most people do with indexes when loading dimension tables? Our loads happen throughout the day (hourly) and obviously so do user queries - doesn't seem to make sense for us to drop indexes during loads. Is it best to just rebuild all bitmap indexes each day (during the night) to clean them up?

Thanks.