SAP Data Quality Management vs Talend Data Quality comparison

"Scalability is good."

"Our primary use case is for us to inspect the results from the product and material, and for releasing or leaving the status of the product."

"We work with API standards or norms for internal applications, so it's essential for SSE to have tests and pass those tests according to the criteria, which makes SAP Data Quality Management very important for our products."

"The solution is customizable."

"I really like the fact that there are no out-of-the-box solutions regarding the development of jobs. Other vendors may have modules which cleanse your addresses. In Talend, you have the freedom to completely develop the process yourself. This can be tricky, but it also makes it fun."

"The most valuable feature lies in the capability to assign data quality issues to different stakeholders, facilitating the tracking and resolution of defective work."

"​It lowers the amount of time in development from weeks to a day.​"

"The numerous components provided by Talend mean you’re able to create jobs quickly and efficiently."

"It offers advanced features that allow you to create custom patterns and use regular expressions to identify data issues."

"We are able to get emails from URLs very easily using this function when others fail."

"It’s easy to monitor the processes. Every morning I’ll open the Talend Administration Center to check the status of the process. Within seconds I’m able to see which process ran successfully and which have failed and why they failed."

"I would like for them to develop a feature to able to record all of our inspections; so all the data can go through SAP. It's not user-friendly or easy to get further analysis, so we mostly skip this step."

"There are some limitations. They are not covering complete scenarios for all the modules."

"SAP Data Quality Management would be better if it directly integrates with the ME system. Right now, the company has a lot of machines on the shop floor working as a standalone, so you have to use all methods to ensure that the data interface appears on the ME system and that SAP Data Quality Management records the QM results. It would be much easier if the ME system could be integrated directly with SAP Data Quality Management."

"There are too many functions which could be streamlined."

"Needs integrated data governance in terms of dictionaries, glossaries, data lineage, and impact analysis. It also needs operationalization of meta-data."

"When we upgraded to Version 6.4.1, we tried using a GIT repository instead of a SVN repository. After a few incidents where things disappeared and changes were not saved, we decided to go back to a SVN repository."

"SQL for displaying underlying data in non-match results does not work."

"Heap space issues plague us consistently. We maxed it out and it runs fine, then it doesn’t, then it does."

"I would say that some of the support elements need improvement."

"They don't have any AI capabilities. Talend DQ is specifically for data quality, which only has data profiling. With Talend DQ, I cannot generate any reports today, so I need an ETL tool. It provides general Excel files, or I have to create some views. If instead of buying a new tool, Talend provides a reporting capability or solution, it would be great. It will reduce the development effort for creating these kinds of reports. We also manage the infrastructure for Talend. From the licensing perspective, for cloud, they only have seat licenses where one person is tied to one license, but for on-premise, they have concurrent licenses. It would be really awesome if they can provide concurrent licenses for the cloud so that if one person is not there, somebody else can use that license. Currently, it is not possible unless a person deactivates his or her license and moves the same seat license to someone else. We are one of the biggest customers in the central zone of the US for Talend, and this is the feedback that we have provided them again and again, but they come back and say that they aren't able to provide concurrent licenses on the cloud. In version 7.3, there is a feature for tokenization and de-tokenization of data. This is the feature that we are looking for. It is useful if somebody wants to see what we have masked and how do we demask it. This feature is not there in version 7.1. There are also a few other capabilities on the cloud, but we don't yet have a big footprint in the cloud."

"If we encounter issues, it’s most likely when using the Talend Open Studio. The studio can be slow, get stuck, or crash. But again, it can be caused by the resources of your machine or your connection with the repository. If we encounter issues with the Studio we restart the Studio. In emergencies, we create and use a new workspace."

"Moreover, the pricing structure stands out as highly competitive compared to other offerings in the market, making it a cost-effective choice for users."

"I would advise to first take a look and at the Open Studio edition. Figure out what you need and purchase the appropriate license."

"We did not purchase a separate license for DQ. It is part of our data platform suite, and I believe it is well-priced."

"It's a subscription-based platform, we renew it every year."

"It is cheaper than Informatica. Talend Data Quality costs somewhere between $10,000 to $12,000 per year for a seat license. It would cost around $20,000 per year for a concurrent license. It is the same for the whole big data solution, which comes with Talend DI, Talend DQ, and TDM."