Fact table size

Hi Experts
Iam working on implementation project, here already some cube are there is a sales, financials & Material Movements cube.
Here Sales and financial cubes are customer define means start with u2018Zu2019.
Here my doubt is how to know the fact table & cubes size? & how to calculate the fact table &
cube size for customer define and SAP define in our SAP BI 7.0 systems .
Regards
SKBABU

Hello,
Check this document:
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0427b8a-7fe5-2c10-f1be-a8be71fa2c06?QuickLink=index&overridelayout=true]
Regards,
Jorge Diogo

Similar Messages

How we will know that dimension size is more than the fact table size?

how we will know that dimension size is more than the fact table size?

Hi,
Let us assume that we are going to take Division and distribution channel in a dimension and assume we have 20 distinct values for Division in R/3 and 30 Distinct values for Distribution channel .So Maximum, we can get 20 * 30 records in dimension table and we can take rough estimation of records in the cube by observing the raw data in source system.
With rgds,
Anil Kumar Sharma .P

Fact table size of the cube

BW Gods!
I need to selectively delete data from a cube which holds data from 2001-2006.....say I want to delete data only for 2001. It was suggested to me by pizzaman in one of our earlier threads that BW would decide if the data to be deleted is more than 10% of the cube size and if it is, it would just copy the cube without the data which has to deleted and it would rename the cube. So he suggested that I should find out the fact table size and make sure that there is enough space in my fact tablespace for this operation to go on.
My question is, how do I find out the fact table size of the cube?
How do I find out if there is enough space on fact tablespace for the above said deletion operation to be executed.
I am not too sure whether I have put across the question correctly. Let me know.
Thank you all in adavance
Ashwin

You want to make sure you include space for the F fact table and the E fact table, assuming you compress the infocube. If you use DB02 and use wild cards you migh be able to get all teh size info in one shot.
Gnerally, he indices for an InfoCube don't occupy a lot of space, but they do take space.
The default InfoCube table space is PSAFACTD and indics are in PSAPFACTI - not 100% sure that is universal acorss all the different DBs. Your shop could also have put them in differnt tablespaces altogether. Probably worth a quick check with your DBAs - they might know that they have lot of space availalbe, and you don't need to take the time to run down the space usage info.
The table copy process will NOT delete the original fact tables unless/until it has successfully loaded to new copy.

Dim Fact table Sizes

Hi Experts,
Could anyone please explain me stats from SAP_INFOCUBE_DESIGNS .
ZABC_C01          /BIC/DZABC_C01       rows:         17    ratio:          5 %
ZABC_C02          /BIC/DZABC_C02       rows:        311    ratio:         88 %
ZABC_C03          /BIC/DZABC_C03       rows:         15    ratio:          4 %
ZABC_C04          /BIC/DZABC_C04       rows:        346    ratio:         98 %
ZABC_C10           rows:    205,786    density:              0.0 %
ZABC_C10          /BIC/FZABC_C10      rows:    205,786    ratio:        100 %
ZABC_C10          /BIC/EZABC_C10      rows:          0    ratio:          0 %
ZABC_C10          /BIC/DZABC_C10P     rows:          2    ratio:          0 %
ZABC_C10          /BIC/DZABC_C10T     rows:        171    ratio:          0 %
Any measures to be taken ?
Appreciating your help Thanks.

Report Writer,
The ration between the each individual dimension rows and the fact table rows. OK. Say that you have 2000 rows in the fact table and 200 entries in the dimension table, that is about 10 times of the dimension size is what you have in your fact table. currently at this rate it is ok, but there are chances for this parity to grow and the ration might become more than 10% of the fact tablke in the future and it is called high cardinality, you need to find ways to minimize that. If you cannot then declare the field as 'line item dimension'. This will help better as this directly stores the sid in the cube, so the join if more efficient.
If you use LISTSCHEMA for a cube and expand the tree structue to look at each table with SE11 or SE16 you will get more idea about the cube and the join and lot more info. This will help you understand better.
Hope this helps.
Alex(Arthur Samson)

How to find Size of the fact table?

hello all
how do i find out the size of the fact table?
Is the size of the fact table is same as size of the cube.
pls let meknow
regards
balji

Hello Balaji,
To find out size of fact table
DB02 ->Detailed anaysis -> Fact table name
It will show you the details.
The size of cube is not exactly equal to the size of fact table, but usually as fact table is much more larger than dimension tables, fact table size will give you a fair idea about cube size.
Hope it helps.
Regards,
Praveen

Size of dimention table fact table ratio question..

Hey Guys !!!
I have very basic question regarding the ratio of size of dimention table and fact table..
its mentioned that the ratio of dim table / fact table sizes should not be greater than 1:20 for performance reasons .. thats OK..
now lets say if i have fact table with customer dim_id ,some other dimention ids , and revenue (KF) .. with 1 million records ..
so ideally my customer dimention table should not have more than 200,000 recods (.ie 200,000 different customers ).
doesnt this put limitation on number of customers in a cube ?
if so, how do we handle this ?
please correct me if i am wrong in interpreting the concept of dimension table.
thanks in advance
swapnil

Hi ASRao ,
thanks for replying ...
you said exactlly what i know ..
sorry i didnt put my question in correct prespective ...
whay i meant was...
lets say , i need to have more than specified (1:20 ) number records in dimension table ,it will definately hamper my reporting performance ...
so, is there any solution to handle this kind of problem ?
like how would i maintain my efficiency of reporting in this case ?
thanks in advance

[Schema Design]: How to reduce inventory snapshot table size

We are planning to store inventory level's periodic snapshot at the end of each day. We have close to 50k different products.
But on a given day only 5-6k products inventory changes.
As I understand if I start inserting just the products which have changed inventory, analysis around semi-additive dimension (Quantity) doesn't work properly.
For better understanding, lets take say the fact table looks like:
product_id time_id quantity
1 1 100
2 1 130
3 1 100
1 30 200
So basically, it says product 1,2,3 from time_id 1 to time_id 29 doesn't have any update in quantity. But product_id 1's inventory changes to 200 on time_id 30.
This approach reduces fact table size by approx 90 rows.
My question is, is it a good idea? Would this semi-additive dimension still give the same result (I doubt though)?
If not, then what other approaches I can take?
Thanks in advance.

Another option is to capture just the net changes (sometimes referred to as a journalized fact table). Then you can create a calculated measure that sums all the changes from the beginning of time up to the current time-slice.
This may seem like an inefficient solution, but there are ways to reduce the problem by limiting the history for which inventory snapshots are available. For example, if the business only needs snapshots for the past 90 days, then you can grab a snapshot
of inventory for all products on day 0, and then capture the net changes for each product for days 1-90. Then you can calculate the snapshot in time by adding the baseline snapshot to the sum of all net changes.
BI Developer and lover of data (Blog |
Twitter)

Fact table is GT Dimension table

Hi All
Where can i find the relation between Fact table and dimension table sizes. If i want to check whether my dimension table is greater than fact table then how?
If i can use program " sap_infocube_designs" then when i am trying to execute it it is not working.
regards
Naga

I dont think SAP_INFOCUBE_DESIGNS doesnt give u the size of the fact table rather the density and the row count in the cube.
"density" in SAP_INFOCUBE_DESIGNS
check the answer by pizzaman in this thread detailing the size of the fact tabe
Fact table size of the cube

Do we have some way to reduce Dimension table size using NLS?

Initially we thought the Cube
archive in NLS would be like:
Replicate Cube in NLS with DAP. DAP creation will create a new structure same like "Star Schema".
While we load data to NLS it deletes from DB.
And hence it reduced size of the DB.
Associated Dimensions will also be replicated in the NLS.
After actually implementation we found :
Fact table size is reducing and DB size with associated E/F fact table is reducing
Dimension tables are still there in DB, and still saving space in DB.
Do we have some other way to reduce Dimension table size using NLS?
As when we are analyzing top 100 tables in SAP BW, we are seeing multiple dimensions are part
of this list.
Thanks,
Jaydip

Hi Jaydip,
Please check below link it might be helpful for you.
http://www.informatik.uni-jena.de/dbis/lehre/ss2011/dbarch/SAP_BW_DB2_NLS_22062011.pdf

How can we know that size of dimension is more than fact table?

how can we know that size of dimension is more than fact table?
this was the question asked for me in interview

Hi Reddy,
This is common way finding the size of cube or dimensions or KF.
Each keyfiure occupies 10 Bytes of memory
Each Char occupies 6 Bytes of memory
So in an Infocube the maximum number of fields are 256 out of which 233 keyfigure, 16 Dimesions and 6 special char.
So The maximum capacity of a cube
= 233(Key figure)10 + 16(Characteristics)6 + 6(Sp.Char)*6
In general InfoCube size should not exceed 100 GB of data
Hope it answer your question.
Regards,
Varun

Size of the DImension and Fact table.

Hi,
I have an info cube, now to decide weather i need to make use of line item or high cardinality .....i need to check or compare the size of the dimension table along with the size of the fact table.
Where do i get this information.
Please help.
Thanks,
Jay.

Hi Friend,
For each infocube you will see Rows and ratio for all the dimension tables and Fact table.
Rows indicate the number of rows in that Dimension or Fact table.
Ratio indicates the number of rows in that table divided by number of rows in the fact table.
As a standard the ratio of rows in Dimension table to rows in fact table should not be more than 10%.
If it is more than you will see it in red colour in this report and you can think of redesigning that particular dimension.
Regards
Hemant Khemani

Determine the size of Dim and Fact table

Hi,
Please some one tell me how do calculate the size of diminsion and fact table
Please explain me step by step.
Thanks

hi
We have two other ways also
Try RSRV test: Elementary > dataBase > DataBase Info about InfoProvide Tables
and You can check out in DB02 tcode Detail Analasys...
Thanks
Khaja

To find the size of the fact table and dimension table

Hi experts,
Can anyone plz tell me if i want to find size of the fact table and size of the dimension table to find cardinality and line item do we first build statistics then find size by transaction DB02 or any other method we have?
Thanks in advance

Hi ,
Please go to Tcode DB02 >Space>Table and Indexes.Give your table name or pattern (like /BIC/F* for gettinf all the Fact tables)
.This will give you sizes of all the table.
Also if you want to get list like TOP 30 Fact tables and Dimension Table.Please use TCode ST14, this will give a desired output with all the required details.
-Vikram

Identify the Cubes where dimension table size exactly 100% of the fact tabl

Hello,
We want to Identify the Cubes where dimension table size exactly 100% of the fact table.
Is there any table or standard query which can give me this data?
Regards,
Shital

use report (se38) SAP_INFOCUBE_DESIGNS
M.

BWA Fact Table Index Size

Hi
Can anybody tell me how the BWA decides when a fact table index gets split into multiple parts? We have a number of very large cubes that are indexed and some have a fact table index that consists of one logical index which is made up of multiple physical indexes but other, similar sized cubes, just have one very large physical index for the fact table.
With the one very large physical index we seem to get an overload problem but when they are split into multiple parts we don't.
Thanks
Martin

Hi Martin,
this depends on the reorg config and the attribute of the index. You can manually trigger a splitting of an index via command 'ROUNDROBIN x', x stand for the number of parts which the index will be split to. Therefore you have to go into trexadmin standalone tool -> landscape right click on index -> split/merge index...
If you want an automatically split, you have to setup your reorg settings. Goto trexadmin standalone tool -> tab reorg -> options -> here you can choose the type of algorithm. Have a look into note 1313260 and 1163149.
Do you have a scheduled reorg job?
Regards,
Jens
PS: Every black box can be understood...

Fact table size

Similar Messages

Maybe you are looking for