SAS Access vs SnapLogic comparison

"The most valuable aspect of the solution is the ease of access to the data in those databases."

"The most valuable part of SAS/ACCESS is what it is made for: connecting to remote systems that are not part of your physical SAS environment."

"The most valuable feature is you have native access to the external databases."

"The solutions ability to connect "snaps" or components to the graphic user interface is very intuitive, prevents errors, and makes implementations easy."

"I would tell others looking into using SnapLogic to use it, take it, use it, and use it, because you can't go beyond SnapLogic and SnapLogic is not going to give you any kind of bad experience, definitely."

"The technical support from SnapLogic is excellent, and I would give it a complete ten."

"I find the reusability and the snaps to be very valuable features."

"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 product is easy to use and has many connectivity options."

"SnapLogic positively impacts my organization, mainly in three areas: speed, system reliability, and maintainability."

"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."

"The solution can provide access to the newer databases that come out sooner."

"The pricing model needs to be reconsidered and adjusted."

"I can't really recall any missing feature or general improvement that is needed. We don't really add too many new kinds of databases and therefore our needs are already met."

"Ultra Pipelines provides real-time ingestion but it needs some adjustment."

"Connecting to data behind enterprise firewalls has been tricky."

"I find the learning curve for complex transformations, the debugging experience, performance optimization visibility, cost for small teams, and version control and DevOps integration could be improved in SnapLogic."

"The problem is that SnapLogic doesn't offer a wide variety of connectors. For example, integrating with Salesforce is not that easy."

"The biggest issue we have faced in our company with SnapLogic is regarding the EDI format"

"We'd like zero downtime in the future."

"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 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."

"The solution's pricing and licensing are expensive."

"The pricing model is complex and is based on modular packages as well as the size of the applicable environment."

"SnapLogic is not expensive. It's reasonably priced."

"From the ROI perspective, the price is extremely high"

"The pricing is okay."

"They have pricing/usage tiers that are easy to move up or down."

"I used the free trial."

"By scaling the solution incrementally the cost is controlled and more beneficial to the client."

"The cost with SnapLogic is an annual license and better than Informatica."

"SnapLogic's price is high compared to the other tools available in the market."