We performed a comparison between Oracle Data Integrator (ODI), SAS Access, and SnapLogic based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."The product has an ELT approach."
"The most valuable features of ODI are the ease of development, you can have a template, and you can onboard transfer very quickly. There's a lot of knowledge modules available that we can use. If you want to connect, for example, a Sibyl, SQL, Oracle, or different products, we don't have to develop them from scratch. They are available, but if it's not, we can go into the marketplace and see if there's a connector there. Having the connector available reduces the amount of hard work needed. We only have to put the inputs and outputs. In some of the products, we use there is already integration available for ODI, which is helpful."
"Oracle provides great documentation."
"All ETL code is stored in repositories in underlying database schemas. The number of users can access and work on the same solution using a client tool. So distributed teams can work on this tool in an efficient manner."
"ODI significantly improves data integration and management by allowing customization of data types from various sources like SQL Server databases."
"ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules."
"It can integrate with more recent databases like Cassandra, Hadoop, and other more recent Big Data databases."
"The Knowledge Module approach provides an easy and reusable way to create our own integration strategies. It's easy to create these Knowledge Modules to connect to new technologies, for instance."
"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."
"SnapLogice is a low-code development tool."
"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's more developer-friendly, and development can be done at a faster phase."
"It is a scalable solution."
"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."
"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 initial setup is very straightforward."
"It has been very good. Just recently, I've faced an issue, but I solved it somehow. While integrating with a file, I faced an issue where I wanted output files, and I had used the text field limited quotations, but at the end of the file, there was a line breakage for the last column. So, we just removed the text field because it was not working correctly for us."
"We used a third party to do the implementation of ODI."
"There are certain things where it can be improved. Initial solution setup seems a bit complex at the start, it should be improved because it becomes bit tough for a novice to get started on this. Sometimes error description is not helpful to understand the problem it gives some generic type of errors which are at times not that helpful to understand the underlying root cause of the issue."
"Stability could be improved because some operators have issues."
"The initial setup is a bit complex compared to other tools."
"If there was an add-on tool to hide the performance issues and solve them for me, then I might be interested in that as it would provide me value."
"ODI could improve by focusing on streamlining its features without unnecessary overhead."
"Oracle Data Integrator (ODI) is already good as a solution. Still, it needs some editing of its preview package, or if the package is upgraded, that will make Oracle Data Integrator (ODI) even better."
"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."
"One area for improvement in SnapLogic is the transparency in the flow of data. It needs to have more transparency. Right now, users only have a preview option at the end of any job flow, so at the end of any Snap Pack, there is a data preview option that lets you review the data and see how it's moving. What would make the solution better is more debugging and more access to change data from the preview panel or more functionality in terms of the preview option."
"There is room for improvement with APM management and how task execution looks."
"It needs some more snaps. I would like to see some of the features be changed in some of the snaps."
"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 support is the most important improvement they could make."
"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."
"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."
