Any Performance Impact Of Partioning With Transactional InfoCubes?

[Former Member]

Dear Colleagues,

I have a customer who is running BW 3.5 and is trying to determine if partitioning their transactional InfoCubes by Fiscal Year will impact performance with BPS?

They had thought they had read somewhere that partitioning of Transactional InfoCubes results in poor write performance?

Thank you in advance for any insights or feedback you may be able to provide.

-M

[former_member93896 · Accepted solution]

Hello Michael,

it depends

1) Only the E-table is partitioned

-> No impact on saving plan data since that inserts only into F-table

2) Only partitioning by period/month

-> If you plan full year, the database has to read 12 partitions from the E-table which is a bit slower than without partitioning.

-> If you plan only a period/month at a time, it will be a bit faster.

3) MultiCubes / Multi Planning Area

-> If you want to combine InfoCubes, you typically need the same partitioning. So if your Actuals InfoCube is partitioned, also partition the Planning InfoCube.

Regards,

Marc

SAP NetWeaver RIG

[Former Member · Accepted solution]

HI Marc,

we have partitioned the infocube used in planning and we dont see the fiscal year variant any more in the planning area master data, how do we fix this error

[Former Member]

Haven't tried on 3.5. I did run into some system problems when I tried to partition a transactional cube on 3.1 (Oracle).

The partitioning only impacts the E fact table, so they must be compressing their InfoCube for the partitioning to even come into play.

Can only partition on FISCPER or CALMONTH.