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

Managing high data volumes

I would like to get some suggestions from those of you that have worked with InfoCubes containing high number of records (millions).

- Which is the maximum number of records an InfoCube can have?

- At what amount of records is recommended to split InfoCubes? (Millions, tens of millions, hundreds of millions)

- Which is the better option for splitting InfoCubes? On time basis, Company ...

- A part from Aggregation, which are the main issues to consider for performance?

Thanks in advance,

Andreu

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 16, 2005 at 06:37 PM
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 16, 2005 at 06:41 PM

    Hi Andreu,

    - I have seen some Cubes with 200 milions data on ORACLE and DB2. I guess the limit depends on the DB ... Anyway I would divide data in different ICs

    - On Oracle I have no problems up to 50 mil data: over some queries become too slow

    - Splitting option it's up to you ... it shold be driven by a criteria that allows parallel execution: I mean IC_A for Company A and IC_B for Company B seen from a Multicube give better results with queries cross company ...

    - See the docs at the following link: https://www.sdn.sap.com/sdn/developerareas/bi.sdn?page=bi_performance.htm: according to me they should be very usefull!

    Hope it helps

    GFV

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 16, 2005 at 06:42 PM

    Andreu,

    Here is my input...

    - Which is the maximum number of records an InfoCube can have?

    I do not think BW has any restrictions as to how many records an Infocube can have.

    - At what amount of records is recommended to split InfoCubes? (Millions, tens of millions, hundreds of millions)

    With the increasing size of fact table, performance goes down. So, obviously if the number reaches 100 million, query performance will take a hit. Generally, for better performance, it would be a good design to see that cube size doesn't go beyond 20-25 million and if does, consider splitting into two.

    - Which is the better option for splitting InfoCubes? On time basis, Company ...

    In most of the cases, this is done on timely basis, like Cube for 2003, Cube for 2004, Cube for 2005 etc and then a multiprovider on top of these. Because most of the report requiremnts will need to see data in 1 year at a time and maintenance and archiving will be easier, as you'll be dealing with only the current year cube. But there could be other affecting factors also, depends on individual situation...

    - A part from Aggregation, which are the main issues to consider for performance?

    COMPRESSION will reduce the number of records and also removes the table partitions (based on requeast ID), which improves performance.

    Maintain Indexes and DB stats.

    Efficient query design. Do not place a lot of chars in 'rows'. Place them in 'Free Chars' instead. Users will expand if needed. Use restrictions in the 'filter' whenever possible.

    restrict the use of 'NAV' attributes, if possible.

    If there is any code for 'user exit vaiables' or virtual infoobjects, try to eliminate the SELECT statements or reduce the DB access if not avoidable.

    Hope it helps

    Gova

    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.