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 Mudrakola on Jul 28 at 7:19 PM
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

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

Hi,

Just a general question, do you really need that much record in the cube for reporting? If the report only show a few lines of summaries info, I would redesign the cube to only store the summaries data. This way the data load will run faster and report runtime will shorter as well. Thanks.

 
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
Mudrakola  
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Earn Recognition for Your Contributions at Toolbox for IT. Gain Points for Community Achievements

_.____.__

0 comments:

Post a Comment

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