Hi Elke,
meanwhile I did some experiments with a simple table (three columns: int_col1 integer
,int_col2 integer ,char_col varchar(50), primary key: int_col, unique key:
int_col2): Each time I inserted 128 rows into this table I determined the total storage
consumption by the data and number of pages for the unique key index (as Daniel
mentioned). Then I made up the ratio of the index storage to the data storage for each
insert.
After 30 inserts the average of this ratio is about 0.4 (40%).
Maybe this average ratio can make up such a supplementary factor for indexes to be
added on the storage consumption for the data. Perhaps there is someone with some SAP
DB experience who can confirm the value of 40% for such a index factor during database
sizing.
kind regards
Frank Schimmelpfennig
PHILIPS Semiconductors Hamburg
ATO-PICTOH IT&DataSupport
Tel.: +49 40 5613 -1835, Fax: -3020
"Zabach,
Elke" To: Frank
Schimmelpfennig/HBG/SC/PHILIPS@EMEA1
<elke.zabach@ cc: [EMAIL PROTECTED]
sap.com> Subject: RE: Storage Consumption of
Indexes
13.03.02 Classification:
16:57
[EMAIL PROTECTED] wrote:
> Hi Elke,
>
> thanks so far! You are right: It is hard (but probably
> possible ;-) ) to calculate the exact storage consumption of indexes!
>
> Since I need only an estimated value for database sizing
> (there are other estimations and adoptions so I do not realy
> need the exact value) is there any experience based
> supplementary factor (maybe in [%]) to cover the storage
> consumptions of indexes and
> to be "on the better side"? - Daniel mentioned such an approach.
>
I do not know any
Elke
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
