Size of a dimension

Can someone explain the following
1. A Dimension table with 10 characteristics consists of 900,000 records
2. The multiple of the SID for all of the characteristics i.e. SID1 * SID2 * ... * SID10
is much greater than 900,000
How is this figure of 900,000 derived? Is this just based on the actual SID values which are loaded via the transactions and the multiple of the SID represents the maximum value that the Dimension table can consist of?
Could anyone through some light onto this? Thanks
If this is the case is there a tool/transaction which I can use to derive which SID values have been used in the cube? Thanks
Message was edited by:
Niten Shah

hi,
have you run the program ? se38 not se39
you will see a list of cubes like
cube1 /bic/d... (dimension table name) rows : xxx ratio : xx %
cube2 /bic/d... (dimension table name) rows : xxx ratio : xx %
cube3 /bic/d... (dimension table name) rows : xxx ratio : xx %
what you need is the ratio
hope this helps.
regards
harikrishna N

Similar Messages

Maximum size of a dimension

Is there a maximum size of a dimension? I know there are limits for the number of properties and the size of a row. However, is there a limit to the overall size of the dimension or a "best practice" as far as sizing dimensions?

Hi,
Based on one of the documents from SAP,
When you are creating dimensions for your application set you should be aware of the following maximums for any one dimension.
u2022 The maximum number of fields in a table (a dimension = 1 table) is 1024.
u2022 The maximum record size is 8064 bytes (a record = 1 row in a table)
The two maximums above relate to the underlying SQL database in which BPC information and data is stored. They need further explanation as to how they relate to a BPC dimension. In BPC a field equals a property. So you can have up to 1024 properties in a dimension. One other factor that has an impact on the actual number of properties you can have in a dimension is the number of levels you have defined. SQL Server creates a set of properties for each level within the dimension. For example, you have 10 properties and three levels in your dimension, your total number of fields is 30. The second limiting factor is the size of the record. To determine record size you have to figure out the number of bytes (a byte equals a character) in each level. Since levels are repeated you only need to figure out the number of bytes in the first level and then multiply that number by the number of levels. To come up with the total number of bytes for a level you simply add up the field size for each field and multiply it by 2 (1 character = 2 bytes).
Hope this gives you some idea.

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

How to reduce jpg file size, not pixel dimensions?

I am preparing images for the web and I really have 2 questions: one about gifs, and one about jpgs.
My standard procedure is to reduce the image to the desired pixel dimensions at 600 dpi
That gives me a crisp small image. then I either use it as is if the file size is low enough (I try for under 600 kb) or convert it to a gif with the save for web and devices tool.
So here are my 2 questions (I will count this solved with either answer)
1) When I convert to a gif I have the 4 boxes: one with original size, the other 3 with options but often the options are too low res for me How do I change my 3 options to start at a higher gif res?
2) If I try to reduce the file size of the jpg in the image size box I set the resolution lower ( 400, 300), which lowers the pixel dimensions and the filesize, but I don't want to cahnge the pixel dimensions. And If I reset the pixel dimensions back to the size I want them, even though it is a lower resolution the file size doesn't change. How to reduce jpg file size using only the resolution, not pixel dimensions? PS I have tried messing with checking and unchecking the 3 little boxes( scale styles, constrain proportions, and resample) but nothing has worked.

Gif is not a great filetype, especially if you want a crisp image. What are your pixel dimensions?
For web, it makes no difference what the dpi is, only the final pixel dimensions so once you have that as you want, use 'Save for Web and Devices' and you can lower the quality - 100% being max and 0% being lowest. I wouldn't save anything below 55%. For a 600kb image, your dimensions must be rather big.

How can we know the size of the dimension(in Line item Dim)?

Hi to all experts,
We use Line item dimension if the size of dimension is 20% or more of the fact table. My doubt is that how can v know that the size of the dimesion is 20% or more of FT?. But we never store MD in dimension tables......So please help me to understand this scenario? Thanks in advance.

Hi
Normally before modelling you will assume the number of entries in your master data and transactional data..
If your dimension is having 3 characteristics
say A,B .....and these characteristic values are say
A---10,000( Total number of master data records)
B----7,000( Total number of master data records)
then your dimenstion would be 10,000 * 7,000 =700000000
in this case you better keep A in a dimension and B in another dimension.
Normally SAP recommends your dimension table shouldnot exceed 100,000...
so whenever you expect a characteristic is having more values then you should make it as line item...
If you want to add a new characteristic to the existing model then you can decide by comparing the ratio of dimension table to the fact table..
Please have a look at the below url for sizes
dimension size
Hope it helps
Thanks,
Teja
Edited by: Teja badugu on Apr 24, 2008 12:19 PM

Change Canvas size on one dimension

I want to change the canvas size to account for a 2 in. leader. E.G. an 8.5 x 11 image to 8.5 x 13 in. But the 2 ins want to be at the lead end of the image, that which enters the printer first.
Thanks in advance for your help.

So set the Anchor in the Canvas Size-dialog accordingly and click Relative, or am I misunderstanding the problem?

Lightroom - FIlter by image size (cropped or dimension)?

Is there no way in Lightroom to filter a catalogue by the image size?
The new filter system in V2 appears compact and tidy, but I can't believe there is not a method to filter by all information contained in the Metadata list? Any help gratefully appreciated. Thanks

_Moon_ wrote:
So, there's nothing I could do within Bridge? Is there any other Adobe application that would be able to do this that isn't Lightroom?
As I stated you can use the Bridge Search (Find) function.

Sort by file size and/or pixel dimensions

I am constantly frustrated by the lack of ability to sort by file size or pixel dimension. I have many versions of the same images, and often want to find the biggest one, or one of a certain size, and it's very time consuming to have to scan all the numbers in the metadata instead of being able to sort. Please add this.
Thanks!

DevMeta will allow you to filter/collect by width and height dimensions.
PixelCountMetadata will allow you to filter/collect by total number of pixels (width x height).
Now that I'm thinking about it, I should probably have just added the pixelcount metadata to DevMeta, but I didnt..., yet...
PS - I dont use PixelCountMetadata, since I only have originals in Lightroom. All resized copies are kept outside of Lightroom. Consider TreeSync if you regularly keep variously sized copies at the ready for various purposes... And, lastly, ExportManager will help you keep all your trees up2date, if you have more than one.
I then use ACDSee to find photos in the exported copies or run slideshows, or serve on the house net, or email...
R

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

Dimension Filter - Dynamic popup size?

Hi,
I have a small problem.
One of my dimension filters have a hierarchy dimension assigned. Depending on the expansion of the preferred hierarchy selection, the user cannot see the whole text.
I know that I can change the size of the Dimension Filter with the settings Popup Width and Popup Height, but is it somehow possible to change the size dynamically depending on the expansion of the hierarchy?
Br
Max Rosén

Hi Max,
As far as I know there is really no such setting in Design Studio that would enable that.
There is also no way how to achieve this with the available scripting methods, if there would be something it would be in theory something like this:
In the OnChange Event of the table cell width where the hierarchy is or based upon the expand level state of the hierarchy in the filterpanel, adjust the width of the filterpanel and the width of the table cell where the hierarchy is.
There should be a solution to do this via javascript, but for that you would need to use the sdk to include some custom javascript code into your bi app.
Normally your requirement can be achieved with/through css, there is a method/way that causes the width of the parent container to expand/adjust automatically when the width of the child element changes. But the problem/difficulty here is, that the filterpanel is created with a lot of absolutely positioned divs (containers) here and there and thus several stacking contexts are created and thus a change in one stacking context has no effect on an element which is in a different stacking context - a change in the width of the table cells where the hierarchy is placed has no effect on some other higher/previously positioned parent container elements because they are in different stacking contexts and when a container's width isn't adjusted too, the inner child element has no way to expand and still be/remain visually nice as a whole.
Anyway, so far I didn't help you much, so here is something you could use to make the text visible/readable without expanding the width:
/* Make Long Text (in Hierarchy) in Dimension Filter Visible (Break Into a New Line) */
#sap-ui-static .sapzenfilterpanel-PopupContainerDialog div.sapUiTableCnt div.sapUiTableCCnt table.sapUiTableCtrl tr.sapUiTableTr > td:nth-child(1),
#sap-ui-static .sapzenfilterpanel-PopupContainerDialog div.sapUiTableCnt div.sapUiTableCCnt table.sapUiTableCtrl tr.sapUiTableTr > td:nth-child(1) span.sapzenfilterpanel-SelectionTableText {
white-space: normal;
/* Optional setting: break to newline anywhere in a word */
/*word-wrap: break-word;*/
(Note: you can simplify/adjust the selectors, this is not the only way how the selectors must look like, it is just an example, but working example...)
A side note when using the setting: "Member Display: Text and Key"
The Dimension filter has 3 columns: 1. Text , 2. Key , 3. Check(boxes)
where the first 2 columns for text and key are the same width. But usually the key is shorter than the text and doesn't need so much space, so you could adjust the width proportions of these first 2 columns so that the text has more width than the column containing the keys:
/* Make Text Column Wider and Key Column Narrower */
div.sapUiTableCnt div.sapUiTableColHdrCnt div.sapUiTableColHdr > div:nth-child(1) {width: 207px !important; /* Default Popup width: 350px > 147px , 147+60=207 */}
div.sapUiTableCnt div.sapUiTableColHdrCnt div.sapUiTableColHdr > div:nth-child(2) {width: 87px !important; /* Default Popup width: 350px > 147px , 147-60=87 */}
div.sapUiTableCnt div.sapUiTableCCnt table.sapUiTableCtrl tr.sapUiTableCtrlCol > th:nth-child(1) {width: 207px !important; /* Default Popup width: 350px > 147px , 147+60=207 */}
div.sapUiTableCnt div.sapUiTableCCnt table.sapUiTableCtrl tr.sapUiTableCtrlCol > th:nth-child(2) {width: 87px !important; /* Default Popup width: 350px > 147px , 147-60=87 */}
Regards
David

Dimension size more than 50%

Hi Gurus,
May I know what are the issues, we will face, if the size of the Dimension table is more than 25%?
In what way it will affect the performance?
Thanks in advance..
Thansk
ananya

Hi,
if you focus on query performance (which is at the end what the users will appreciate the most) then be very cautious when flagging a dimension as line item...
As per my experience the 20% as threshold to flag a dim as line item is too low; I flag it when its cardinality is more than 70 even 80% and if I can afford it!
Indeed when having many characteristics it is sometimes very expensive to use only one dim for one charateristic!
It all depends on your data distribution and how your organize the characteristics in your dimensions. You cannot take for granted that if you are loading billing documents and post the billing document number in your cube "you should put the doc num in a line item dimension"... Simply because in my case, billing documents have in average more 50 items...
You should first try to analyze where is you system spending the most of your 10 minutes...
- could an additional index on one of the dimension table help?
- is your report using navigational attributes? perhaps an aditional index on the X table and/or P table could help a lot...
- do you collapse your cube?
- do you use aggregates?
- are all the indexes created and regenerated from time to time (avoid degenerescence)?
- are your statistics updated?
- which RDBMS are you using? Oracle can really be fine tuned...
- do you use partitioning? Physical and/or logical?
They're so many spots to tune in order to have an effincient BI system.... but one thing is for sure: 10 minutes is definitively too loooong... As a matter of fact, I start to wonder when the average time for a navigational step is more than 7 seconds in my system....
hope this helps...
Olivier.

IPhone photo default size / dimension is too big - Fix?

iPhone space is expensive
When we take a photo with the iPhone (3g and 4s-at least), it's approx 2MB (for a jpg)!
We can have more room in iPhone storage for more music, photos, etc...
My Windows-7 detects the phone and Windows-Explorer auto-opens; therefore, I can drill down into phone/files - only to the photos and simply drag-um-over. They're all huge!
Printing a 2MB pic is big enough to cover a whole bed-room wall.
We should be able to set this to: 1 MB, 512K, 256K
- or set defualt photo dimensions
New cameras are the same (even if JPG is selected)
With some cameras, users can set a default picture-size / or rather dimensions re: 4x4, 3x5 (or 10x8, 12x12, 12x14) and the like...
This results in tiny file size.
Note:
JPG is a deviation from MPG
MPG came first as MPEG (audio + video)
Motion Picture Experts Group (MPEG) developed so a surgeon in New York, can assist (video-conference) w/a operation in Los Angeles

So... is there a question in there at all? Fail to find a ??? in the multicolored text....
And if a piddly 5MP 4S is giving you hiccups, wait till you run across an 8MP i5!

Logo Link size/dimensions?

Good Morning,
Can someone what the size and/or dimension limits are for the Logo link on a Email Security Virtual Appliance 600V?
Thank you,
Joe

Spoke w/ Joe earlier via email ---
Why is my company logo not displayed in encrypted envelope via CRES?
From an active CRES account, please verify the following:
The Envelope Profile on the CRES account and the Email Encryption Profile Name on the Email Security Appliance (ESA) must match.
Logo should be at most 60x160 pixels, less than 100kb.
Applies to .gif and .jpg files only.
Since the CRES servers do sync based on periodic schedules, there are times where the logo may take up to 24 hours to propagate. Most of the time this should occur within 1 hour.
For setting up more than one logo you may use the Multi-Branding feature introduced in AsyncOS 7.0.
-Robert

Follow-up on u0093Fact Table VS. Dimension relative sizeu0094

You dont have to read the background info. below, it is only for reference. I have already gone though several links as such your touch in your own words will be much appreciated.
Can you help me understand these which came from the many links the Experts referred me .
1. For better performance: Use line item dimension where applicable, but use the "high cardinality" option with extreme care. Any clarification on high cardinality? And why with extreme care?
2. For better performance: 1. Make the Index perfect and create secondary index based on requirement.. I dont seem to follow this index issue being raised here.
Thanks.
--Background: References from these past postings ---
There is much to be said about performance in general, but I will try to answer your specific question regarding fact and dimension tables.
First of all try to compress as many requests as possible in the fact table and do that regularily.
Partition your compressed fact table physically based on for example 0CALMONTH. In the infocube maintenance, in the Extras menu, choose partitioning.
Partition your cube logically into several smaller cubes based on for example 0CALYEAR. Combine the cubes with a multiprovider.
Use constants on infocube level (Extras->Structure Specific Infoobject properties) and/or restrictions on specific cubes in your multiprovider queries if needed.
Create aggregates of subsets of your characteristics based on your query design. Use the debug option in RSRT to investigate which objects you need to include.
To investigate the size of the dimension tables, first use the test in transaction RSRV (Database Information about InfoProvider Tables). It will tell you the relative sizes of your dimensions in comparison to your fact table. Then go to transaction DB02 and conduct a detailed analysis on the large dimension tables. You can choose "table columns" in the detailed analysis screen to see the number of distinct values in each column (characteristic). You also need to understand the "business logic" behind these objects. The ones that have low cardinality, that is relate to each other shoule be located together. With this information at hand you can understand which objects contribute the most to the size of the dimension and separate the dimension.
Use line item dimension where applicable, but use the "high cardinality" option with extreme care.
Generate database statistics regularily using process chains or (if you use Oracle) schedule BRCONNECT runs using transaction DB13.
Good luck!
Kind Regards
Andreas
There are some simple things by which we can maintain the performance.
1> Make the Index perfect and create secondary index based on requirement.
2> Make statistics perfect.
3> Based on data size in dimenssion table use lineitem dimenssion.
HOpe this will help you.
Suneel

Hi Caud..
1] High Cardinality..
High Cardinality means that this dimension contains a large number of characteristic values. This information is used in accordance with the individual database platform in order to optimize performance. For example, an index type other than the standard may be used. Generally a dimension is perceived to have high cardinality when the dimension is at least 20% the size of the fact tables in terms of the number of entries each contain. Avoid marking a dimension as having high cardinality if you are in any doubt.
Cardinality creates indexes on the Dimension table entries and there by you would see an improvement in performance.
With Oracle DB, setting the Cardinality option causes a b-tree index to be built instead of a bitmap index even if it is not a line item dim.
Setting it as a Line Item dim also causes a b-tree index to be built instead of a bitmap index, but also embeds SID directly in the fact table, eliminating the dimension table.
As it changes from bit map to B-tree, u have to be careful as the SAP recommends the Bit map.
2]As indices increased the performance tremendously, u have to consider when ever the performance is main factor. it is very easy for query to access the data in the data target if it already indexed.
Refer this link..
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Hope it helps-
Regards-
MM
Assign points if it is useful, it is right way to say thanks.
Message was edited by: vishnuC

Should my dimension table be this big

Im in the process of building my first product dimension for a star schema and not sure if im doing this correctly. A brief explanation of our setup
We have products (dresses) made by designers for specific collections each of which has a range of colors and each color can come in many sizes. For our UK market this equates to some 1.9 million
product variants. Flattening the structure out to Product+designer+collection gives about 33,000 records but when you add all the colors and then all the colors sizes it pumps that figure up to 1.9million. My “rolled own” incremental ETL load runs
ok just now, but we are expanding into the US market and our projections indicate that our products variants could multiple 10 fold. Im a bit worried about performance of the ETL just now and in the future.
Is 1.9m records not an awful lot of records to incrementally load (well analyse) for a dimension table nightly as it is never mind what that figure may grow to when we go to US?
I thought of somehow reducing this by using a snowflake but would this not just reduce the number of columns in the dimensions and not the row count?
I then thought of separating the colors and size into their own dimension, but this doesn’t seem right as they are attributes of products and also I would lose the relationship between products, size & color I.e. I would have to go through the
fact table (which ive read is not a good choice.) for any analysis.
Am I correct in thinking these are big numbers for a dimension table? Is it even possible to reduce the number somhow?
Still learning so welcome any help.
Thanks

Hi Plip71,
In my opinion, It is always good to reduce the Dimension Volume as much as possible for better performance.
Is there any Hierarchy in you product Dimension?.. Going for a snowflake for this problem is a bad idea..
Solution 1:
From the details given by, It is good to Split the Colour and Size as seperate dimension. This will reduce the vloume of dimension and increase the column count in the fact(seperate WID has to be maintained in the fact table). but, this will improve the
performance of the cube. before doint this please check the layout requirement from the business.
Solution 2:
Check the distinct count of Item varient used in fact table. If it is very less, they try creating a linear product dimension. i.e, create an view for the product dimension doing a inner join with the fact table. so that only the used Dimension member will
be loaded in the Cube Product Dimension. hence volume is reduced with improvement in performance and stability of the cube.
Thanks in advance, Sorry for the delayed reply ;)
Anand
Please vote as helpful or mark as answer, if it helps Regards, Anand

Size of a dimension

Similar Messages

Maybe you are looking for