Re: Help on newbie admin

The answers to both of your questions are almost entirely dependent on your application. Some general info that may help:

Obviously, SYSTEM, TEMP, RBS, TOOLS, USERS, INDEX should all be in separate tablespaces. Typically, larger tables / projects should each go in separate tablespaces - this makes for easier managing and moving to redistribute I/O. You can usually group several smaller, similar tables together in the same tablespace, provided they aren't update intensive, and don't all get accessed at the same time.

As far as sizing goes, again, this is dependent on your application, and really your preferences. You can size the tablespace to hold as much initial data as you want, 30 days, 6 months, 1 year, etc. All depends on how often you want to monitor the tablespaces and how often you want to add datafiles, or allow your existing datafiles to autoextend. To size the tablespace, you need to know how big each record in each table in that tablespace is, how many records will be added during a defined time period (such as a month), and then decide how long you will retain the data. For each table you would than have (x transactions of y size per day, times 31 days = monthly data size). Be sure to allow yourself some fluff for internal overhead such as rowid, etc.

HTH In article <758ngn$eo8$1_at_ionews.ionet.net>,   Ryan Richards <rrichard_at_gibson.ns.ionet.net> wrote:
> I have just a few questions that I was hoping to get answers for from some of
you experienced Oracle people.
>
> #1 Do you normally use a seperate tablespace for each project or clump them
all in one tablespace? (or does that change depending on the circumstances)
>
> #2 How do you know how big to make the tablespace? Do you aim low and add
space as you need it? Whats agood starting point?
>
> Thanks for the help,
> Ryan R.
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Wed Dec 16 1998 - 13:18:34 CST