decision criteria repository vs maintable

[Former Member]

I am looking for some decision criteria whether you should have one repository with several main tables versus several repositories with only one main table. In MDM 7.1 of course..

Regards,

Heleen

[former_member198313 · Accepted solution]

Hi Heleen,

it simply depends on the business requirement.

However one criteria is size as well.

Also, I dont think to keep more than 2 main tables in one repository.

Now the business requirement case is:

if Services and customers are 2 repositories. if customer require some dependability on both service and customer, then its better to keep in one repository. if they are not required to be dependent on each other and will be seperate entity, its better to keep seperate.

Howerver there were requirements from several customers to have more than 1 master talking to each other and hence this functionality was provided.

in simple words; relationships between master object types (customer, product, employee) is required.

Hope this helps,

+ An

• This is not an official message and not related to my organization.

[Former Member]

Hi Heleen,

It is better to go with 1 Repository with multiple maintables if there is going to be frequent interaction between the maintables else go for multiple repositories.

[Former Member]

Hi Heleen,

As stated by An, it completely depends on the relationship between the two masters. From technical point of view, if two masters are sharing the same lookup tables like UoM ISO Code etc then you are required to modify only once if any changes are to be made in this table if you are using one repository since both the masters are refering only one table while if there are two repositories then you need to change the table of both the repositories.

There are various advantages and disadvantages of both the approaches

Advantages of maintaining one repository

1. Size required is less since the masters shares the same lookup tables

2. Easy to maintain e.g. lookup table updation

3. Easy to Transport e.g. only one archive is to be taken

Disadvantages

1. If your DBMS crashes you will loose the data for all the masters

2. Little bit complex as compare to maintaining two repositories

Advantages of multiple repositories

1. Robust as compare to approach 1

2. Simplicity

Disadvantages

1. Double the efforts if the common lookup table is to be updated

2. Occupy more disk space

3. In order to transport, archive of all the masters is required.

It completely depends on your requirement, if the masters are linked then Approach 1 would be better else Approach 2

Regards,

Jitesh Talreja

[Former Member]

Thank you for your answer. I will use it in our decisions.

Has anybody articles about this issue?

Regards Heleen

[former_member198313]

no Heleen,

There is still no article for this.

+ An

• This is not an official message and not related to my organization.