We performed a comparison between IBM InfoSphere MDM, Microsoft MDS, and SAP Master Data Governance based on real PeerSpot user reviews.
Find out what your peers are saying about SAP, Microsoft, TIBCO and others in Master Data Management (MDM) Software."The advantage is that the matching engine is very good, so that's why customers generally prefer it. From the inbuilt data model perspective, IBM MDM is good."
"There are not really many areas of the product that need improvement because the product stays up-to-date with data management needs."
"The features that are most valuable are the governance, the end-profiling and the ETL which allows you to see the metadata repositories."
"When users update their information on one product, the data is sent to a database. My approach was to maintain a master data record, ensuring that each platform loads the latest updated record. Instead of having three separate records, the system keeps one master data record, storing the historical records for reference."
"The ease of use is valuable."
"Enables non-technical people to directly interact with the BI system."
"It is very easy to deploy and provision a machine."
"The most valuable feature is the administration console."
"The solution is easy to install."
"Unlike specialized tools, MDS is adaptable for various industries, making it a versatile choice for master data management."
"What I like about Microsoft, is that it has a huge database with many users."
"Technical support is very good."
"Some of the features that I have found to be beneficial are the search and uploads functions."
"The data capturing and data governance features are valuable."
"The scalability is very good."
"Useful for building master data."
"Validates all aspects from security to authorization and authentication."
"We've managed tens of thousands of updates within 30 to 60 minutes, and we can also replicate these changes to all connected systems."
"The product is easy to use and is beneficial from a data governance perspective."
"It is a stable solution."
"The tool is difficult to understand from a customer perspective and for developers."
"We also want better cloud integration, so we could do things in the cloud if we needed to. This would be a good feature to add in a future release."
"IBM InfoSphere MDM's UI is complicated. It also needs to improve its on-prem configuration."
"The product is really only created for large organizations."
"It would be a better option to have an on-cloud version."
"In the next version, I would like to see integration with Azure."
"I do not like using Silverlight and Internet Explorer. The new 2019 version gets rid of that, which is one of the reasons why we are looking to switch."
"JMD repositories have records that come in thousands and millions, which takes a long time to process."
"Microsoft MDS isn't getting strong support because Microsoft is focusing more on cloud solutions."
"There are occasions when the solution maintains SD and we get duplications of MDS."
"The only drawback is that it does not have the matching, merging, and all true MDM components. For these, you have to use another competent called Data Quality Services (DQS). You need to plug it in and use it along with MDS for true MDM. Both of these are integrated together, but you have to do them separately, whereas, in Profisee, there are a couple of screens where you can configure the matching process, create matching rules, and other things, and everything is in one product, which is not the case with MDS. In order to implement a true MDM, you need MDS, DQS, and SSIS. You have to use MDS to store your golden records, DQS to configure and standardize all your rules and matching percentages, and SSIS to load the data to DQS and MDS. At the same time, you also need Melissa Data to clean up your addresses to validate and standardize the addresses. That's the main component of true MDM. It would be good if they can create a true matching component inside MDS and merge MDS and DQS."
"Microsoft MDS' language should be simple so everyone can use it easily."
"The profiling feature, especially for materials, needs improvement. We faced challenges maintaining specific details for a single material from multiple vendors."
"The user interface is not user-friendly."
"They should improve the solution's performance as sometimes the process consumes much time."
"The multidomain MDM feature is based on EIP systems, which may not be a good model for all master data."
"It does not ensure data matches after system upgrades."
"There were challenges with handling multiple values within a single input field at the screen level."
"The price can be improved."
"It could be more user-friendly."
