SAS Access vs SnapLogic comparison

"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 aspect of the solution is the ease of access to the data in those databases."

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

"SnapLogic is an IPA tool that leverages a low code environment to connect to multiple sources, extract data, and store it in Azure data lake."

"The API architecture makes it easy for orchestration."

"It is a scalable 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."

"I find SnapLogic to be user-friendly, especially for beginners with limited experience in data engineering or ETL."

"The solution could improve its API management."

"It's more developer-friendly, and development can be done at a faster phase."

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

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

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

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

"There is room for improvement with APM management and how task execution looks."

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

"SnapLogic doesn't provide any on-premises software, so users have only cloud-based software to use."

"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 isn't ideal for complex processing or logic. We use another solution for that."

"It needs some more snaps. I would like to see some of the features be changed in some of the snaps."

"The dashboards regarding scheduled tasks need further improvement."

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

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

"When comparing it with solutions like Apigee or MuleSoft, it still offers better value."

"The license model is based on consumption."

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

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

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

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

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

"It is a higher initial cost than other easy-to-use integration apps."