Hi Gurus,
I have some concerns with Data Modeling a master data Infoobject into an Infocube. The master data object will have hundreds of millions of rows. It is for my realignment process that will have ship-to/material, so I really have no choice about the number of records I need to store.
Does anybody have any data that can support the general experience in terms of performance of :
a) adding records to the MD object and
b) querying the Cube?
Shall I store the MD object as a line-item dimension for better query performance?
Regards,
Alex
Hi,
I do not understand really well your problem...
You have got millions of rows in a MD like MATERIAL with a compound SHIP TO.
So you should avoid having both of them in the same dimension of your cube if the same MATERIAL code can be delivered to several SHIP TO partner. Otherwise, no problem to put them together into the same dimension.
regards
Hi Alex:
In addition make that dimension as "High Cardinality" in addition to Line-Item dim.
Laoding Master Data has nothing to do with many records in CUBE. So, you cube load will be slower.
You should look into CUBE partitioning, etc to fine tune queries on CUBE.
Ram C.
Is there any way you can break out the data into mulitple infocubes, that all look the same, except for the data?
For instance, If you have multiple sales orgs, you could create mulitple infocubes (one for each sales org), and put a multiprovider on top of it, to keep the info contents low, but the data will only be accessed when needed (it wouldn't all be stored in the same tables....).
That may help performance.
/smw
Add a comment