We performed a comparison between SnapLogic 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."I found SnapLogic valuable and what I found most valuable about it was its ETL feature. I also found its automation feature valuable. It can be used for automating manual activities. It can be used as a middleware for certain transactional data processing and minimal datasets and ETL activities."
"The product is easy to use and has many connectivity options."
"SnapLogic is a great platform for establishing integrations among various systems or patterns by using any kind of interface. If something is not supported by predefined snaps – snaps are connectors in SnapLogic – you can create them (custom snaps) or write a script."
"The connection with SOAP is the best feature."
"It is a scalable solution."
"The API architecture makes it easy for orchestration."
"It is a stable solution."
"The solutions ability to connect "snaps" or components to the graphic user interface is very intuitive, prevents errors, and makes implementations easy."
"I have used most of the standard SQL features, but the ones that stand out are the Data Flows and Bulk Import."
"It is easy to set up. The deployment is also very quick."
"It is easy to set up the solution."
"The setup is straightforward. It's very easy to install."
"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."
"It's a competent product."
"It's saved time using visualization descriptions."
"The technical support is very good."
"I am looking for more scheduling options. When it comes to scheduling, there are different tools in the market."
"SnapLogic sits somewhere in the middle. It doesn’t offer enough easy canned integrations for its users like some of the easier to use integration apps."
"One of the areas for improvement in SnapLogic is that the connectors for some of the applications should be more available in terms of testing in the dev environment. Another area for improvement is that the logging should be standardized, for example, the integration with an ELK stack should be required out-of-the-box, so you can ship the log and have it in the ELK stack. There should be integration with ELK stack for the log shipping."
"There is room for improvement with APM management and how task execution looks."
"I would like to see more performance-related dashboards, ones that display the cost of a pipeline, for instance. Also, it would be helpful to have management dashboards for overseeing pipelines and connections."
"Connecting to data behind enterprise firewalls has been tricky."
"What could be improved in SnapLogic is that it was not capable in terms of processing a large number of datasets, but at that point, SnapLogic was evolving. It didn't give a lot of Snaps. I heard recently there are a lot of Snaps getting added and the solution was being enhanced, particularly to connect different data sources. When I was working with SnapLogic six months to one year back, I faced the issue of it not being capable of handling a huge volume of datasets or didn't have much of Snaps, and that was the drawback. If there is any large number of data sets, that's based on or depends on your configuration. If it is a huge volume of data, other traditional ETL tools such as Informatica and Talend can process millions and billions of records, while in SnapLogic, the Snaplex fails or it returns an error in terms of processing that huge volume of data. Informatica, Talend, or any other ETL tool can run for hours in terms of jobs, while SnapLogic jobs fail when the threshold is reached. SnapLogic isn't able to withstand processing, but I don't know if that's still an issue at present, because the solution is getting enhanced and it's been more than six months to one year since I last worked with SnapLogic. There are now a lot of Snaps getting added to the solution, and if it can overcome the limitations I mentioned, SnapLogic could be the go-to tool because currently, it's not being used as much in organizations. It's being used comparatively less compared to other retail tools."
"One area for improvement in SnapLogic is the transparency in the flow of data. It needs to have more transparency. Right now, users only have a preview option at the end of any job flow, so at the end of any Snap Pack, there is a data preview option that lets you review the data and see how it's moving. What would make the solution better is more debugging and more access to change data from the preview panel or more functionality in terms of the preview option."
"It should have other programming languages supported as well from a scripting perspective. Currently, only C# and VB.NET are supported, which limits it to .NET. It should have Java support as well."
"I would like to see more standard components out of the box, such as SFTP, and Data Compression components."
"The security could be improved, as it is more important in our context."
"At one point, we did have to purchase an add-on."
"The solution could improve by having quicker release updates."
"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."
"It's difficult to refactor SSIS. It gets cumbersome to reuse the solution."
"Performance could be better."
SnapLogic is ranked 14th in Data Integration with 20 reviews while SSIS is ranked 2nd in Data Integration with 69 reviews. SnapLogic is rated 8.0, while SSIS is rated 7.6. The top reviewer of SnapLogic writes "Easy to set up, easy to use, and is low-code". On the other hand, the top reviewer of SSIS writes "Maintaining the solution and contacting its support team is easy". SnapLogic is most compared with Azure Data Factory, AWS Glue, IBM InfoSphere DataStage, Informatica Cloud Data Integration and Alteryx Designer, whereas SSIS is most compared with Informatica PowerCenter, Talend Open Studio, IBM InfoSphere DataStage, Oracle Data Integrator (ODI) and Boomi AtomSphere Integration. See our SSIS vs. SnapLogic report.
See our list of best Data Integration vendors and best Cloud 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.
Snaplogic
I've found Matillion to be very intuitive and easy to use...
I wish I could answer that question, but my expertise is limited to SSIS only.
As far as I know 'talend' could be a better choice compare to the other tools.
you can address your question to our SAP department solutions@jet-bi.com
Informatica is the way forward
it depends on the infrastructure you are using and what's the total cost of ownership being authorized for the implementation. You can see the "Data Integration" partners within AWS-Redshift in the below link-
aws.amazon.com
Informatica undoubtedly is one of the best in the list. It's a great ETL tool but surely expensive in License.
Microsoft's SSIS is a light weight tool but not as robust as Informatica. Certain other software's like Talend and Matillion are also good. Talend has an open source option where developers can build their own APIs and then productionize those APIs and that's cost effective as well.
Traditionally SQL is a plus, automation is only by a ETL is smarter.
Any ETL tool that moves data to it's own server for processing will add overhead and will not use Redshift's power ( more specifically parallelism). It is recommended to use standard SQL for data processing.