We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

Re: [sap-bw] Cube Design Constraints

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from ucrao on Jul 28 at 7:48 PM
identify unwanted/historical data and load by selection. as ashok said use line item dimensions and optimise other dimensions. combine unrelated characteristrics it can improve performance to avoid number of table joins. for reporting performance you can create aggregate on chars which consists large volume of data.

Thanks

rao

---------------Original Message---------------
From: Mudrakola
Sent: Tuesday, July 28, 2015 7:27 PM
Subject: Cube Design Constraints

Hi
1. Make one of the dimension with heavy load as line item dimension in Cube1
2. Use line item dimension in Cube 2 too.
3. Optimize the dimension size. Add a dimension for the fields which are rarely getting updated and find a subgroup in one dimension and make it as separate dimension
4. Record length has nothing to do with data load as it depends on the table keys.
Last but not least, the issue is with modeling and you are looking for solution else where . At least per my knowledge.
Regards,
Ashok

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2015 Ziff Davis, LLC. and message author.
Ziff Davis, LLC. 28 E 28th Street New York, NY 10016
ucrao  

achievements
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Become a blogger at Toolbox.com and share your expertise with the community. Start today.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language