Change Tracker Performance Impact

[Former Member]

MDM: 7.1

CE: 7.2

ERP: 6.0 EHP4

Hi,

We are currently using CE/BPM based central master data management. A custom application is being developed for collaborative master data authoring.

As part of the MDM configuration, the client wishes to track changes on MDM records for audit purposes. We are looking at the MDM Change Tracking facility provided by SAP but not sure about the performance impact it will have on the MDM server.

We have over 300 attributes for the object we wish to track for changes. Not all attributes will change all the time but it is expected that the overall number of changes every month will be over 1000, each change including approx 20-30 fields. The number of users is expected to be approx 15 initially but will increase over time.

I have seen on SCN forums people talking about potential performance degrade by enabling change tracking. Has anyone actually experienced performance degrade due to enabling change tracking for MDM records? If so, have you tried any means to keep the impact low e.g. by allocating more resources to MDM server?

Thanks and regards,

Shehryar

Edited by: Shehryar Khan on Dec 2, 2010 1:39 PM

[Former Member]

Hi,

Change histoey does have impact on system performance. this can be controlled via regular archiving of Change History database. Lets say, Change history table data older than 3 months can be stored in another repository.

Second option could be to export all Change History data(Older than 1-2 days) to a BI system(using regular scheduled job), and have change hisotry report there. It will bring drastci change in MDM System performance. 1-2 days data can be viewed from MDM Change history database itself.

Regards,

Prashant

Edited by: Prashant Malik on Dec 3, 2010 1:58 AM

[Former Member]

Hi again

To add to what others mentioned- we can also try to optimize the number of attributes enabled for change tracking.

Also within change tracking we have 3 options for tracking- Additions, Changes and Deletion. We need to see which ones to select. There is also scope of reducing the change tracking rows in applications in peak times.

For ex- For the initial data loads we can disable change tracking and after data load is complete you can revert back.

Hope this helped-Ravi

[Former Member]

HI Ravi,

Thanks. We have considered these factors. However, it would be great to see some more information on the performance degrade actually experienced by customers.

Regards

[Former Member]

Prashant, I know this is an old post, but could you provide me with more details on how to "Second option could be to export all Change History data(Older than 1-2 days) to a BI system(using regular scheduled job), and have change hisotry report there"

I am investigating doing this, but of course the MDM syndicator can not send the change tracker data to BI, so what other otions are there?  Windows scheduler?

[Former Member]

Yes, there's a performance penalization by activating the changes tracking. However, if you are talking about 15 users, it should not render "unusable". I'd add more RAM to the MDM Server and make sure the link between the database and the MDS is steady and as fast as possible. also, be ready to see the database increase in size.

Kind regards

Alejandro