Re: Disk Space Prediction

        For each table you need to know the maximum number of rows that are to be stored in the database along with an estimate of average row size. Then build a table and let Oracle do the arithmetic for you. BTW, don't forget to estimate the space for the indexes.

        Finding out the maximum sizes is your real problem. You have to find out what the relationships are between number of rows added to a table and the underlying business transaction. For example, for each sale one row is added to the invoice header table and an average of five rows are added to the invoice detail table. Another example, one row is added every month to the General Ledger table for each distinct account in the table. This is information the developers should be able to tell you.

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 6/24/00, 5:39:42 AM, thiko_at_my-deja.com wrote regarding Disk Space Prediction:

> Hi
 

> I have some developers who will soon be ready to want to have many
> tables, indexes, data etc put onto our live database in their
> appropraite tablespace. My querry is as to what the rule is/how you
> work out whether you have enough disk space for this? We are on sun
> disks. I have monitoring in place so I can predicte space when their
> work is in the database and growing but I need to know if in the
> beginning there will be enough disk space before I put it on.
 

> Would appreciate any suggestions...
 

> Many thanks.
 

> Thiko!

> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Sun Jun 25 2000 - 00:00:00 CDT