Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Information of Tablespaces

Re: Information of Tablespaces

From: Ethan Post <epost1NOepSPAM_at_yahoo.com.invalid>
Date: 2000/08/04
Message-ID: <21c698a0.5868ab4b@usw-ex0104-031.remarq.com>#1/1

Jay,

Check out the Oracle Conepts Manual. It is likely you will end up doing the following.

Here is the minimum.

  1. Separate all objects on to 2 tablespaces, one for indexes and one for data, make sure they are on different disk controllers/volumes.

It tends to get more complex from there and everyone will have their own opinion of what is best. You could go to 4 tablespaces, 2 for data and indexes associated with low activity tables and 2 for the data and indexes associated with high growth tables. There is somthing called "Locally Managed Tablespace" (I think) that you could look at using, this will help in preventing fragmentation with your fast growing tables. Also you are going to want to make sure you fast growing tables are grabbing big extents. I believe it is best to keep the same extent size for tables within a tablespace, thus one of the reasons you will want to put your larger tables on a different tablespace.

This is just my opinion, I'm still a bit of a newbie, only 2 years experience but this is the gist of what I have been seeing and reading in regards to this. Ideally you want to pick up a few Oracle books that go into more detail about design and optimization.

-Ethan

http://www.freetechnicaltraining.com
http://www.gnumetrics.com


Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free!
http://www.keen.com Received on Fri Aug 04 2000 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US