We performed a comparison between Microsoft MDS, Talend MDM Platform, and TIBCO EBX 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."It is very easy to deploy and provision a machine."
"The most valuable feature of Microsoft MDS is its management."
"It's very easy to use."
"One of the main features I have found useful is the integration with Azure active directory."
"The best thing about it is that it comes with the Microsoft package."
"It has a very good feature called Excel plug-in. You just have to install the plug-in, and then it directly connects to the MDS instance where you can maintain and manage your data and publish it right through Excel. You don't need to go to the front end to make any changes. It has easy integration with SQL Server, and you can use SSIS to do the ETLs. It is a part of the Microsoft stack. It works with most of the Microsoft stuff."
"Technical support is very good."
"What I like about Microsoft, is that it has a huge database with many users."
"What I like about the Talend MDM Platform is that it's a good vendor diagnostic tool."
"The API and the data model are very valuable features."
"The data modeling is very good."
"The data quality is very good."
"The initial setup is easy and straightforward."
"The product is extremely flexible."
"The tool's UI is good and easy to understand."
"It is a very stable solution...It is a scalable solution."
"There are a lot of possible use cases for this Master Data Management tool."
"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."
"Microsoft MDS isn't getting strong support because Microsoft is focusing more on cloud solutions."
"It would be a better option to have an on-cloud version."
"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."
"In the next version, I would like to see integration with Azure."
"The solution could be better integrated into Microsoft's other products."
"There are occasions when the solution maintains SD and we get duplications of MDS."
"From my understanding, MS, as of 2021, will not maintain the product going forward."
"What's missing in the Talend MDM Platform is that it's not maintaining technology references. For example, my company needs a reference case if the platform has been implemented for a configuration that's similar to the client's required configuration. Currently, the client is still reluctant to roll out the Talend MDM Platform at a wider level because there's still no reference received from the Talend team."
"The product does not scale well horizontally. We find the scalability to be quite inferior to other options."
"In terms of improvements that this solution needs, it should support big data."
"We would like to see the community an documentation for this solution be developed. At present there is very little tutorial documentation available, and limited community support for issues with the product."
"Currently, users can't use Plain SQL queries in TIBCO EBX."
"The tool has to improve mapping and workflow. It should be made more robust."
"Everything is updated through forms, and working with UI web forms. It's more record-based processing. It is not mass-based processing. This is one of the things that are not good for TIBCO EBX. Another problem is we cannot join tables and prepare a view where the tables are joined. Someone can code it but it is not a feature of the solution without code. You have to take data from a table, combine it with data from another table and then present it. This could be done better."
"The initial setup can be a bit complex."
"The documentation needs improvement."
