7.1 table and index fragmentation

We just received our development copy of 7.1 and have noticed a very nice feature which allows tables to be stored in separate dbspaces from their respective indexes. We were trying to figure out how much room to allocate to an index dbspace. Can anyone recommend a strategy for this configuration? Does it make sense to devote an entire dbspace to just indexes or should dbspaces contain both tables and indexes that don't relate to each other? Thanks in advance for any advice. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ Rick email: rlewis@ssnet.com ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~