Limit on number of Main tables in a repository

[former_member218126]

Hi experts,

Is there any limit on number of main tables being maintained in a repository? Do we face any performance issue or any such issue if we maintain 20-30 or more main tables in data model? Please share your experience or any documentation link if any.

Thanks,

Vineet

[Former Member]

there is no technical limitation ...

as long, u think u can maintain them - go ahead - create 50 of them !

havent come accross any scenario though that requires more than 2 !

plz share ur scenario - is it a WHO project ??

thanks

-Adrivit

[former_member278106]

Hi,

In the MDM 7.1 sizing guide there are sizing estimations for standard repositories with one main table. You'll need to multiply the sizing parameters (SAPS, memory, disk space) that you receive using the sizing formulas to a number of main tables in your repository.

Regards, Lev

[Former Member]

Hi Vineet,

In Latest version of SAP MDM which is 7.1 we have the liberty to use multiple Main tables so answer to your question is yes we can use 20-30 main tables, now the question is that what type of data model you are prepairing this question is just to understand your entire structure and may be suggest some thing at higher level on which you can think and then take corrective action as per your thoughts.

Generally even if you are integrating Customer/Products in single repository and then designing the main table you wont have to prepare such huge number of main tables you can have these two main tables and then rest of then as sub tables and refer it to each other also you need to know what imapct it will have on system performance becuase they would be referring to each other and also if you are creating some thousands of records in each repository then it is more advisable to use limited number of main tables and use MDM to it's fullest capability by designing such model that we have best utlisation of server performance.

Hope it helped a bit.

Let me know if you need any further information on same.

Thanks and Regards

Praful.

[former_member182007]

Vineet Kumar -

First of all it depends on your data model. I don't understand what kind of model you are preparing for which landscape and what kind of MDM solution. Please share some insights , as it would be a learning for us as well.

secondly, it is always suggessted that you maintain major amount of fields in main table and rest references can be handled in Lookups. so you can have multiple main table which signifies the interconnected/linked object in landscape. ofcourse after that only it provides a meaningful meaning. isn't it ..?

Also consider the impact Repository loading/unloading time and your real time user who will use the application. more on sizing you can refer MDM sizing guide.

HTH

thx

Deep

[cweissheimer]

Please refer to [this thread|; for more information:

BR,

Carlos

[Former Member]

Hey,

Generally there is no limit on Number of Main tables in a Repository.

But 20-30 Main tables look a little too much, please make sure that you have optimized the data model, only a fraction of data need to be maintained as a Main table, everything else can be lookup tabales.

Thanks

Aamir