Re: Calculating table and index sizes

In article <32giet$660_at_panix.com> gmr_at_panix.com (George Reichert) writes:
>I have a table:
>
>invoice_number char(14)
>page_number number(2)
>line_number number(3)
>invoice_line varchar2(80)
>
>There is a concatenated primary key on this table (invoice_number,
>page_number, line_number).
>
>Let's assume I have 100,000 rows in this table. Is there an EASY
>way to calculate the size of this table and its index.

Simply look in the Server Concepts Manual, chapter 5, where it explains how to figure out the overhead for the keys and rowid.

Now if you want an _accurate_ way, that's another story. Since varchar2 is variable sized and at the end of the record, you have a variable recordsize. I take it you are trying to estimate disk requirements, so the easy way is to take the size you calculated above and double it. And remember, disks are down to $1000/gig. You can spend more than that in programmer hours trying to mess around with too little disk space.

-- 
Joel Garry           joelga_at_amber.rossinc.com            Compuserve 70661,1534
These are my opinions, not necessarily those of Ross Systems, Inc.
%DCL-W-SOFTONEDGEDONTPUSH, Software On Edge - Don't Push.  
panic: ifree: freeing free inodes...