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."The API architecture makes it easy for orchestration."
"It's more developer-friendly, and development can be done at a faster phase."
"The solution could improve its API management."
"The solutions ability to connect "snaps" or components to the graphic user interface is very intuitive, prevents errors, and makes implementations easy."
"You can use other languages, such as Python, and easily connect to other systems."
"The connection with SOAP is the best feature."
"The feature I found most valuable in SnapLogic is low-code development. Low-code development has been very useful for simple processes, which is required for business users such as extracting details from a file or getting things reported by calling your web service. Calling your web service also becomes easier with SnapLogic because of the snaps available, so if you have the documentation, you can call an API. You don't have to write all those clients to call an API, so that is another feature I found very easy in SnapLogic. Configuring and managing all the file systems also become very handy with the solution."
"What I found most valuable in SnapLogic is the ETL feature, particularly the Transform Snap Pack, for example, any kind of reading or writing on Transform Snaps. Other than that, all the third-party connectivity tools such as the SAP Snap Pack, Salesforce Snap Pack, Workday Snap Pack, even the ServiceNow Snap Pack, I find all those are pretty useful in SnapLogic."
"It has the ability to be deployed into the cloud through Data Factory, and run completely as a software as a service in the cloud."
"The solution is stable."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"It is also easy to learn and user-friendly. Microsoft is also good in terms of technical support. They have built a large community all over the world."
"There are many good features in this solution including the data fields, database integration, support for SQL views, and the lookups for matching information."
"The workflow features have been very valuable. You can have automated workflows and all the steps are controlled. The workflow functionality of integration services is excellent."
"The initial setup of this solution is very straightforward."
"SSIS' most valuable feature is its reporting services."
"We'd like zero downtime in the future."
"It needs some more snaps. I would like to see some of the features be changed in some of the snaps."
"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."
"They should expand in terms of features for SaaS-based market requirements in different sectors."
"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."
"I am looking for more scheduling options. When it comes to scheduling, there are different tools in the market."
"SnapLogic doesn't provide any on-premises software, so users have only cloud-based software to use."
"I don't think the support has better knowledge about technologies and tool support. There were lots of times when we had an issue, and it took me quite a long time to explain the problem. I feel like some of the support staff don't know their product well."
"The solution could improve by having quicker release updates."
"It hangs a lot of the time."
"We have a stability problem because when something works, it works one time. The next time, it doesn't work."
"It would be nice if you could run SSIS on other environments besides Windows."
"We'd like more integration capabilities."
"SSIS is cumbersome despite its drag-and-drop functionality. For example, let's say I have 50 tables with 30 columns. You need to set a data type for each column and table. That's around 1,500 objects. It gets unwieldy adding validation for every column. Previously, SSIS automatically detected the data type, but I think they removed this feature. It would automatically detect if it's an integer, primary key, or foreign key column. You had fewer problems building the model."
"Options for scaling could be improved."
"The performance of SSIS could improve when comparing it to Oracle Database."
SnapLogic is ranked 14th in Data Integration with 21 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 IBM InfoSphere DataStage, AWS Glue, Azure Data Factory, 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 Informatica Cloud Data 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.