|
You should build your new tablespaces using locally managed tablespaces with ASSM. You can create them with auto-allocate extents or fixed size extents. I almost always opt for fixed uniform size extents. This way all the extents are the same size in the tablespace and can be reused by any object.
As far as sizing, you have to remember that an extent can only hold one object. If you create large extents and place indexes in them, there could be a lot of wasted space. On the other hand, locally managed tablespaces do not hit the data dictionary for extent information and having many extents will not impact performance.
There is no need to try and import a table into one extent. My recommendation is to create one tablespace for indexes and another for tables. Make the table tablespace extent size equal to the smallest table you are going to place in it (if you have some large tables with very small tables you might need to make larger extents and have some wasted space with the small tables). Make the index tablespace extents smaller since the objects are smaller. Don't worry about a table that ends up with 100 extents; it will not impact performance.
Another alternative is to create small, medium and large tablespaces and divide up your objects into these tablespaces depending on object size.
|
