Skip to Content

MDM in a landscape with extreme master data volume & volatility

I'm interested in any statistics relating to the performance of MDM in landscapes where tens of millions of master data records are managed, and have very high volatility (i.e. >10k master data changes per day).

I've read most of the collateral available and can't see any clear guidelines or warnings. Obviously, infrastructure plays a major part in performance, but I'd be very interested in any examples or studies.

Thanks, <i><b>Andy</b></i>

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on May 06, 2004 at 02:47 PM

    Hi Andy,

    In general, as you pointed out there are a number of factors including the infrastructure, server types, network latency etc that can play a big role in determining the answer to your question. We generally see such large volume requirements coming in from specific industries such as banking and retail and continue to incorporate them into our release planning. We currently cannot provide you with specific numbers given the sheer number of factors involved as mentioned above and additionally, such factors such as time difference between triggers, whether the changes follow a bell curve distribution in terms of throughput etc. As you can imagine, there are a number of variables involved.

    We would rather suggest that if you are involved in an MDM implementation, to contact the SAP project lead who will then work with us with respect to your specific requirements. Generally speaking, MDM sizing information is based on ongoing performance tests and is communicated to SAP implementation teams through SAP Field Service once a project has been initiated.



    Add a comment
    10|10000 characters needed characters exceeded

    • Thanks Sunil.

      We're at the assessment stage at the moment, and are planning several feasibility workshops. I've been in contact with the SAP-MDM product manager for the UK (CB), and he's been very helpful, and will be contacting him again with the specifics of our customers requirements.

      Thanks again, <i><b>Andy</b></i>

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.