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

Physical Partitioing Calender Year

HI Gurus.

Cube is physically partitioned on 0Calmonth.

Report is running on Calender Year Example - 2007 and 0calmonth2 Example - 005 not on 0Calmonth Example - 2007005.

Does phy part still improve performance.

Thankyou Gurus

Message was edited by:

George M

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 02:27 PM

    Table partitions are physically separated tables, but logically they are linked to one table name. PSA tables and non-compressed F-fact table are partitioned by the system (by request ID). The (compressed) E-fact table can be partitioned by the user by certain time characteristics. For range-partitioned InfoCubes, the SID of the chosen time characteristic is added to both fact tables.

    When using range partitioning, query response time is generally improved by partition pruning on the E fact table: all irrelevant partitions are discarded and the data volume to be read is reduced by the time restriction of the query. Note that all F fact table partitions have to be read.

    The number of (range) partitions is one more than defined. This additional partition keeps all time characteristics higher than the upper limit. Example: monthly partitions 01/2007 – 12/2007. This creates 12+1 partitions. The first one contains records from 01/2007 and earlier, then there are 11 partitions containing the months 02 – 12/2007. An additional partition for all records after 12/2004 is created.

    In ORACLE, report SAP_DROP_EMPTY_FPARTITIONS can help you to remove unused or empty partitions of InfoCube or aggregate fact tables. Unused or empty partitions can emerge in case of selective deletion or aborted compression and may effect query performance as all F fact table partitions are accessed for queries on the InfoCube.

    Hope it Helps

    Chetan

    @CP..

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 07:44 AM

    I think it will not improve performanc as it is partitioned for 2005 and not for other years. If the partition is done on calmonth for all years teh it would improve performance i believe.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 03, 2007 at 08:00 AM

    Hi,

    As your cube is partitioned for the year 2007 and query is running for calmonth 02 it will directly retrive data from that partition only so it will improve the performance. when you partitioned your cube based on 0calmonth system will partition according to that like 12 + 2 partitions, when ever data comes it will be stored in the respective partitions and will be retrived from them at the time of query execution.

    Regards

    Sankar

    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.