Calculating size of CUBE & ODS

Question

Hi Everybody,
   Could any one suggest me, how can we calculate exact size of the cube & ODS?
Thanks and Regards,
Ramesh

Answer 1

DB02 can provide some history on a table or tablespace about space consumption, but not row count, e.g.
For a specific table like this -
Date............Size (Kbyte) 
10/01/2005 ........1,193,984
09/01/2005 ........1,193,984
08/01/2005 ........1,128,448
07/01/2005 ........1,020,928
06/01/2005 ..........988,160
05/01/2005 ..........955,392
04/01/2005 ..........914,432 
03/01/2005 ..........881,664
02/01/2005 ..........840,704
01/01/2005 ..........807,936 
12/01/2004 ..........635,904
11/01/2004 ..........521,216
But you don't really want to have to collect this for all the tables involved on a monthly basis.
SAP_INFOCUBE DESIGNS can provide row counts
0BWTC_C03  /BI0/D0BWTC_C031    rows:  6,005  ratio:  1 %
0BWTC_C03  /BI0/D0BWTC_C03P    rows:     83  ratio:  0 %
0BWTC_C03  /BI0/D0BWTC_C03T    rows:    880  ratio:  0 %
0BWTC_C03  /BI0/E0BWTC_C03     rows:616,772  ratio: 84 %
0BWTC_C03  /BI0/F0BWTC_C03     rows:116,037  ratio: 16 %
RSRV test - Database information about InfoProvider, can provide this info about a InfoProvider -
ZPU_C51 tables
ZPU_C51 is a BasisInfoCube
Cube ZPU_C51 has 9 dimensions; 0 dimensions are line item dimensions
  Table /BIC/DZPU_C511 has 3962 entries. Size corresponds to 3% of the InfoCube
  Table /BIC/DZPU_C512 has 2243 entries. Size corresponds to 2% of the InfoCube
  Table /BIC/DZPU_C513 has 4847 entries. Size corresponds to 3% of the InfoCube
  Table /BIC/DZPU_C514 has 5843 entries. Size corresponds to 4% of the InfoCube
  Table /BIC/DZPU_C515 has 44 entries. Size corresponds to 0% of the InfoCube
  Table /BIC/DZPU_C516 has 148 entries. Size corresponds to 0% of the InfoCube
  Table /BIC/DZPU_C51P has 174 entries. Size corresponds to 0% of the InfoCube
  Table /BIC/DZPU_C51T has 74 entries. Size corresponds to 0% of the InfoCube
  Table /BIC/DZPU_C51U has 5 entries. Size corresponds to 0% of the InfoCube
  Table /BIC/EZPU_C51 has 0 entries. Size corresponds to 0% of the InfoCube
  Table /BIC/FZPU_C51 has 142233 entries. Size corresponds to 100% of the InfoCube
Keep in mind the row counts displayed by SAP_INFOCUBE_DESIGNS and RSRV are based on the DB statistics and are only as current as the last time statistics have been collected on the tables.
SE16 on the other hand, actually goes out and runs a query on the table to provide a true current row count.
From a storage mgmt standpoint, I doubt your DBA is really that concerned about the number of rows you added and really just wants to know about disk storage consumption trends.  Mgmt on the other hand may very well be interested in row counts as it is something they can relate to and can indicate what's going on in the organization.
I am not aware of any BW functionality that provides current InfoProvider row count histories/trends other than to run some of the above tools monthly or write your own pgm to do so. 
There are various tables that track load information and could provide counts of records added. You could probably create an Infoset and do some reporting that way. The best way to get counts of records loaded is probably from the BW Tech Content cubes where you could create a query to provide monthly record load counts by InfoProvider, e.g.
Calendar day     Time      Records
9/1/2005     38,950     5,789,428
9/2/2005     77,581     19,185,224
9/3/2005     1,138     248,247
9/4/2005     1,066     241,527
9/5/2005     260     528
9/6/2005     21,352     5,192,199
9/7/2005     28,954     5,212,939
9/8/2005     25,770     5,837,173
9/9/2005     34,271     6,341,234
9/10/2005     834     13,580
9/11/2005     1,193     242,951
9/12/2005     19,426     4,408,503
9/13/2005     20,756     3,504,421
9/14/2005     24,353     3,975,332
9/15/2005     30,432     5,984,105
9/16/2005     31,633     6,077,860
9/17/2005     799     15,682
9/18/2005     1,152     243,567
9/19/2005     16,288     4,038,754
9/20/2005     15,313     3,504,187
9/21/2005     22,744     3,955,414
9/22/2005     29,216     5,348,904
9/23/2005     28,798     5,616,426
9/24/2005     696     13,151
9/25/2005     2,010     242,341
9/26/2005     15,279     3,666,828
9/27/2005     22,411     4,095,785
9/28/2005     23,465     4,547,366
9/29/2005     30,920     5,826,502
9/30/2005     32,039     6,294,938
Overall Result     599,100     119,665,096
Keep in mind that records added to a cube for a month are not be the same as the records that end up in the E fact table table after compression.
So I think you really need to define what it is you are looking for, statistical info for mgmt and/or info for the DBA for storage estimates.
For stoage planning purposes, your DBA should be able to determine space use and trends, that's a basic function of their job.  Your role is to keep them informed of changes they can't determine from the DB, e.g.
- transaction volume expected to double for an InfoProvider
- you are going to create several aggregates
- creation of new InfoProviders
- you are deleting large amoutns of data
BW disk storage grows - I don't think I have ever seen a Data Warehouse that has reached a point where it rolls off as much data as it loads.  A new BW can easily have storage requirements increasing by multiples year over year the first few years.  It can waste a lot of folks time trying to get to fussy about tracking individual table changes.
Haven't used the Quicksizer to off an opinion. Probably an acceptable tool for estimating, just like any of the row count methods others have mentioned.