Skip to Content
author's profile photo Former Member
Former Member

Precautions b4 compressing plannng cube?

Hi

we've a transactional cube that has around 25 requests with 20 month old data & each request averages around 20000 records. Interestingly, the cube was never compressed.

At this point, I feel, compressing the cube might improve performance.

I'd like to know any precautions that I need to know before hand.

I see one problem is, we'll be out of options to delete compressed requests on individual basis. Any other issues?

what is the best bet to back up this cube & its data incase to retrieve it back to original cube status?

Is there any check list to make sure nothing went wrong after compression for comparing pre-compresstion step & post-compression steps?

Appreciate your ideas / suggestions.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 25, 2004 at 08:34 AM

    Hi,

    you can find all the info you need in the OSS Note 407260

    'FAQs: Compression of InfoCubes' (if you have a DB Oracle)... and in http://help.sap.com/saphelp_bw30b/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/content.htm

    What's the meaning of compression on an individual basis ?!

    In order to come back I think it's not possible.(excluding a back-up restore option..)

    Let me know if this is not enough...

    Hope it helps.

    Bye,

    Roberto

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 25, 2004 at 02:15 PM

    I would compress transactional planning cubes regularly if you don't switch and load data into the cube. Why? There is no need or sense to delete a transactional request from such a cube because you don't know what data is in the request and how it affects records in latter requests.

    Best regards

    Dirk

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.