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."Besides loading data, we do most of our transformations in ODI."
"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."
"Easy to understand, very developer-friendly, and has a big forum community and lots of documentation for support."
"ODI is a very accessible tool, especially since the mapping functionality has been added."
"It's completely user-friendly."
"The product has an ELT approach."
"I do not have to maintain a separate ETL instance. I can change the SQL when something is not performing correctly."
"I like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support."
"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."
"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 solution is easy to implement and easy to use. It's basically just drag and drop."
"The API architecture makes it easy for orchestration."
"It's more developer-friendly, and development can be done at a faster phase."
"By using snaps instead of functions in code, you can see the building blocks of the integration visually. This helps a lot."
"The product is easy to use and has many connectivity options."
"The solution could improve its API management."
"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 lacks some functions and features."
"ODI could improve by focusing on streamlining its features without unnecessary overhead."
"If you have something like Cisco on top of it, you will have endless problems."
"Reverse engineering is complicated and challenging to manage."
"The initial setup is a bit complex compared to other tools."
"Technical Support could be better."
"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."
"We used a third party to do the implementation of ODI."
"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 am looking for more scheduling options. When it comes to scheduling, there are different tools in the market."
"The dashboards regarding scheduled tasks need further improvement."
"They should expand in terms of features for SaaS-based market requirements in different sectors."
"SnapLogic should have some inbuilt protocol mechanism in order to speed up."
"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."
"The solution isn't ideal for complex processing or logic. We use another solution for that."
"The support is the most important improvement they could make."
"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."
