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 feature is you have native access to the external 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."

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

"The initial setup is very straightforward."

"Overall product rating is nine out of ten."

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

"The API architecture makes it easy for orchestration."

"You can use other languages, such as Python, and easily connect to other systems."

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

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

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

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

"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 dashboards regarding scheduled tasks need further improvement."

"The setup cost would be four or five. There would be only one point of improvement if the price could be lower."

"I am looking for more scheduling options. When it comes to scheduling, there are different tools in the market."

"The solution isn't ideal for complex processing or logic. We use another solution for that."

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

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

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

"The pricing is okay."

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

"The license model is based on consumption."

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

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

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