We performed a comparison between SAS Access, SnapLogic, and SSIS based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."The most valuable feature is you have native access to the external databases."
"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."
"SnapLogic is more user-friendly than Boomi in terms of debugging. You can move the mouse to a place, and it will record and show the data easily."
"The connection with SOAP is the best feature."
"The solution could improve its API management."
"Despite having no prior experience in SnapLogic, we managed to build, test, and prepare it for release in just three hours, handling heavy data efficiently."
"You can use other languages, such as Python, and easily connect to other systems."
"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 solution is easy to implement and easy to use. It's basically just drag and drop."
"It is a scalable solution."
"The setup was easy. All Microsoft products are easy to set up."
"Built in reports show package execution and messages. Logging can also be customized so only what is needed is logged. There is also an excellent logging replacement called BiXpress that provides both historical and real-time monitoring which is more efficient and much more robust than the built-in logging capabilities. And none of this requires custom coding to make it useful unlike many other ETL tools."
"Data Flows are the main component we use. These can range from a simple source to sink ETL, to many source to many sink dataflows."
"It is easy to set up the product."
"The performance is good."
"It's a competent product."
"It's saved time using visualization descriptions."
"The most valuable feature of SSIS is that you can take data from other servers which are not MS SQL Server or Oracle."
"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."
"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."
"The problem is that SnapLogic doesn't offer a wide variety of connectors. For example, integrating with Salesforce is not that easy."
"I am looking for more scheduling options. When it comes to scheduling, there are different tools in the market."
"Ultra Pipelines provides real-time ingestion but it needs some adjustment."
"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."
"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."
"SnapLogic doesn't provide any on-premises software, so users have only cloud-based software to use."
"SSIS doesn't have a very good user interface, but if you can work with it, it'll provide you with almost all of the functionality."
"We have a stability problem because when something works, it works one time. The next time, it doesn't work."
"It's a legacy tool, that is nearing the end of its useful life."
"We've had issues in terms of the amount of data that is transferred when we are scheduling."
"Sometimes we need to connect to AWS to get additional data sources, so we have to install some external LAN and not a regular RDBMS. We need external tools to connect. It would be great if SSIS included these tools. I'd also like some additional features for row indexing and data conversion."
"We would like the solution to be expanded so that it is available for other platforms than just Microsoft."
"The solution should work on the GPU, graphical processing unit. There should also be piping integration available."
"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."
