We performed a comparison between IBM Cloud Pak for Data and SSIS based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Its data preparation capabilities are highly valuable."
"The most valuable features of IBM Cloud Pak for Data are the Watson Studio, where we can initiate more groups and write code. Additionally, Watson Machine Learning is available with many other services, such as APIs which you can plug the machine learning models."
"One of Cloud Pak's best features is the Watson Knowledge Catalog, which helps you implement data governance."
"You can model the data there, connect the data models with the business processes and create data lineage processes."
"The most valuable features are data virtualization and reporting."
"Scalability-wise, I rate the solution a nine or ten out of ten."
"DataStage allows me to connect to different data sources."
"It is a scalable solution, and we have had no issues with its scalability in our company. I rate the solution's scalability a nine out of ten."
"In SSIS, the scope is not only to handle ETL challenges, but it will allow us to do so many other tasks, such as DBA activities, scripting, calling any .exe or scripts, etc."
"SSIS is easy to use."
"Built in reports show package execution and messages. Logging can also be customized so only what is needed is logged. There is also an excellent logging replacement called BiXpress that provides both historical and real-time monitoring which is more efficient and much more robust than the built-in logging capabilities. And none of this requires custom coding to make it useful unlike many other ETL tools."
"The solution is stable."
"The performance is better than doing it in some alternative ways. We don't have to worry about so much manual work."
"It's already very user-friendly and has a good dashboard."
"It's something I needed for bulk imports. I'm not a big fan of it, but I haven't seen anything better."
"It's saved time using visualization descriptions."
"Cloud Pak would be improved with integration with cloud service providers like Cloudera."
"One thing that bugs me is how much infrastructure Cloud Pak requires for the initial deployment. It doesn't allow you to start small. The smallest permitted deployment is too big. It's a huge problem that prevents us from implementing the solution in many scenarios."
"The tool depends on the control plane, an OpenShift container platform utilized as an orchestration layer...So, we have communicated this issue to IBM and asked if it is feasible to adapt the solution to work on a Kubernetes platform that we support."
"The product is trying to be more maturity in terms of connectors. That, I believe, is an area where Cloud Pak can improve."
"One challenge I'm facing with IBM Cloud Pak for Data is native features have been decommissioned, such as XML input and output. Too many changes have been made, and my company has around one hundred thousand mappings, so my team has been putting more effort into alternative ways to do things. Another area for improvement in IBM Cloud Pak for Data is that it's more complicated to shift from on-premise to the cloud. Other vendors provide secure agents that easily connect with your existing setup. Still, with IBM Cloud Pak for Data, you have to perform connection migration steps, upgrade to the latest version, etc., which makes it more complicated, especially as my company has XML-based mappings. Still, the XML input and output capabilities of IBM Cloud Pak for Data have been discontinued, so I'd like IBM to bring that back."
"The product must improve its performance."
"The technical support could be a little better."
"The solution could have more connectors."
"I have a tool called ZappySys. I need that tool to cut down on the complexity of SSIS. That tool really helps with a quick turnaround. I can do things quickly, and I can do things accurately. I can get better reporting on errors."
"We've had issues in terms of the amount of data that is transferred when we are scheduling."
"Sometimes when we want to publish to other types of databases it's not easy to publish to those databases. For example, the Jet Database Engine. Before the SSIS supported Jet Database Engine but nowadays it doesn't support the Jet Database Engine. We connect to many databases such as Access database, SparkPros databases and the other types of databases using Jet Database Engines now and SSIS now doesn't seem to support it in our databases."
"The debugging could be improved because when it came to solving the errors that I've experienced in the past, I've had to look at the documentation for more information."
"I would also like to see full integration with our BI because then our full load of data will be available in our organization. They should incorporate an ATL process."
"This solution needs full support for real-time processing."
"The solution could improve by having quicker release updates."
"I would like to see better technical documentation because many times information is missing."
IBM Cloud Pak for Data is ranked 17th in Data Integration with 11 reviews while SSIS is ranked 2nd in Data Integration with 69 reviews. IBM Cloud Pak for Data is rated 8.0, while SSIS is rated 7.6. The top reviewer of IBM Cloud Pak for Data writes "A scalable data analytics and digital transformation tool that provides useful features and integrations". On the other hand, the top reviewer of SSIS writes "Maintaining the solution and contacting its support team is easy". IBM Cloud Pak for Data is most compared with IBM InfoSphere DataStage, Azure Data Factory, Informatica Cloud Data Integration, Palantir Foundry and Denodo, whereas SSIS is most compared with Informatica PowerCenter, Talend Open Studio, IBM InfoSphere DataStage, Oracle Data Integrator (ODI) and AWS Glue. See our IBM Cloud Pak for Data vs. SSIS report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
