We performed a comparison between Actian Pervasive Data Integrator [EOL], SSIS, and StreamSets based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."There were no concerns with the stability. This product is very good from a stability perspective."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"The main value of any Microsoft product is the ease of use. You can achieve more with less time. That's what's beneficial for me. With many competitors, you might need to spend more time coming up with a solution because you have to focus on taking care of the product."
"The debugging capabilities are great, particularly during data flow execution. You can look into the data and see what's going on in the pipeline."
"The setup was easy. All Microsoft products are easy to set up."
"SSIS integrates well with SQL servers and Microsoft products."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"The performance is good."
"The ability of SSIS to transform and transport data is extremely valuable to me. It allows for intelligent extraction and manipulation of data during the process. Improved error handling would enhance ETL processes further. I haven't directly utilized the data flow components but they seem capable of supporting complex data integration needs."
"It's very easy to integrate. It integrates with Snowflake, AWS, Google Cloud, and Azure. It's very helpful for DevOps, DataOps, and data engineering because it provides a comprehensive solution, and it's not complicated."
"The most valuable feature is the pipelines because they enable us to pull in and push out data from different sources and to manipulate and clean things up within them."
"For me, the most valuable features in StreamSets have to be the Data Collector and Control Hub, but especially the Data Collector. That feature is very elegant and seamlessly works with numerous source systems."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"I really appreciate the numerous ready connectors available on both the source and target sides, the support for various media file formats, and the ease of configuring and managing pipelines centrally."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"I am not sure if there are various connectors available in the recent version of Pervasive DI to support the wide range of sources available (e.g., big data, cloud, EME)."
"We would like the solution to be expanded so that it is available for other platforms than just Microsoft."
"We'd like more integration capabilities."
"It's a legacy tool, that is nearing the end of its useful life."
"I would like to see more features in terms of the integration with Azure Data Factory."
"It needs more integration tools, so you can connect to different sources."
"There was also not enough instructions from Microsoft in regards to this application or this technology, which can easily be improved upon."
"When I compare Talend and SSIS, Talend provides more features. With Talend, we can handle a large volume of data. Talend is usually used to treat a large volume of data, which makes it better than SSIS on the data side. Talend also has a very good Talend Management Console to schedule the jobs and do other things. It can also be easily connected to version control tools such as GitHub or SVN. The last time I used SSIS, it was connected through TSS for the Windows Console version. I am not sure it has been improved or not. If it is not improved, Microsoft should improve it. They should change the product to provide another console."
"The security could be improved, as it is more important in our context."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
"Using ETL pipelines is a bit complicated and requires some technical aid."
"The execution engine could be improved. When I was at their session, they were using some obscure platform to run. There is a controller, which controls what happens on that, but you should be able to easily do this at any of the cloud services, such as Google Cloud. You shouldn't have any issues in terms of how to run it with their online development platform or design platform, basically their execution engine. There are issues with that."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
Earn 20 points
