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

Cube or Multicube - what and why??


Can someone tell me what are the pros and cons of reporting on a Cube or a Multicube. What is better and why?



Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 25, 2005 at 02:54 AM

    Have a look at OSS note 629541 before you jump to conclusions about poorer performance on MultiProviders. User RSRT (aggregate option) to see the actual reads against the different InfoProviders. You may find you need to target your restricted keyfigure at a particular InfoProvider, by restricting by InfoProvider (under datapackage), if you feel there are too many reads.

    My experience has shown that I can get the performance I need from a multiprovider, and it makes managing the datawarehouse so much simpler. If for instance I have a actuals loading daily, but a budget is only loaded annually (perhaps a few times before it is right), and perhaps forecasts are loaded monthly. I would always separate into different cubes and combine with a multiprovider.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi!

      Multiproviders are not always slower than the cubes. sometimes it can be used for improving the performance.the performance completely depends on your model. IF planned properly we can get performance improvements from multiprovider. using multiproviders improves the flexibility in reporting because some times underlying datastructures may be changed like in case of slowly moving dimension scenario.

      with regards


  • Posted on Aug 24, 2005 at 07:13 PM

    Hi Nikki,

    Basically the structure of both these objects is the same, i.e. both are multidimensional in nature. One possible advantage that I have seen is that by reporting off a multiprovider you have the flexibility to combine another data target to your scenario. We have done this once where we started off with one part of the application and just had one cube as a part of the multiproivder. All reports were off the multiprovider and we later added another cube to this multiprovider without impacting the queries and user favourites.

    Sometimes it is better to have several smaller cubes and a multiprovider than all the data in one large cube. The multiprovider queries are broken up into sub queries (for each data target) that may be executed in parallel.

    With multiprovider queries however you need to be a bit careful when understanding what data will be available for what set of chars and how it will roll up. Sometimes it is useful to set constant selections in this case.

    Hope this helps...

    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.