We performed a comparison between Pentaho Data Integration and Analytics, SSIS, and Unifi based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration.
"Lumada has allowed us to interact with our employees more effectively and compensate them properly. One of the cool things is that we use it to generate commissions for our salespeople and bonuses for our warehouse people. It allows us to get information out to them in a timely fashion. We can also see where they're at and how they're doing."
"Flexible deployment, in any environment, is very important to us. That is the key reason why we ended up with these tools. Because we have a very highly secure environment, we must be able to install it in multiple environments on multiple different servers. The fact that we could use the same tool in all our environments, on-prem and in the cloud, was very important to us."
"The fact that it enables us to leverage metadata to automate data pipeline templates and reuse them is definitely one of the features that we like the best. The metadata injection is helpful because it reduces the need to create and maintain additional ETLs. If we didn't have that feature, we would have lots of duplicated ETLs that we would have to create and maintain. The data pipeline templates have definitely been helpful when looking at productivity and costs."
"The amount of data that it loads and processes is good."
"I can create faster instructions than writing with SQL or code. Also, I am able to do some background control of the data process with this tool. Therefore, I use it as an ELT tool. I have a station area where I can work with all the information that I have in my production databases, then I can work with the data that I created."
"The solution has a free to use community version."
"We're using the PDI and the repository function, and they give us the ability to easily generate reporting and output, and to access data. We also like the ability to schedule."
"It makes it pretty simple to do some fairly complicated things. Both I and some of our other BI developers have made stabs at using, for example, SQL Server Integration Services, and we found them a little bit frustrating compared to Data Integration. So, its ease of use is right up there."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"You can get data from any data source with SSIS and dump it to any outside source. It is helpful. Getting, extracting, converting, and dumping data doesn't require much effort because we can do everything in the user interface. You drag and drop, then give the required input. It's intuitive."
"The most valuables features are the relatively short learning curve, and the automation capabilities provided through the BIML add-in for SSDT."
"The setup was easy. All Microsoft products are easy to set up."
"We like that this solution includes a developer edition, free of charge, to allow for training."
"The initial setup was easy."
"I have found its most valuable features to be its package management capabilities and the flexibility it offers in designing workflows."
"The controller makes it easy to control everything from one platform. The management is easy."
"It's easy to manage and support the user, our guests, and our customers if they have a problem."
"Parallel execution could be better in Pentaho. It's very simple but I don't think it works well."
"The web interface is rusty, and the biggest problem with Pentaho is debugging and troubleshooting. It isn't easy to build the pipeline incrementally. At least in our case, it's hard to find a way to execute step by step in the debugging mode."
"I was not happy with the Pentaho Report Designer because of the way it was set up. There was a zone and, under it, another zone, and under that another one, and under that another one. There were a lot of levels and places inside the report, and it was a little bit complicated. You have to search all these different places using a mouse, clicking everywhere... each report is coded in a binary file... You cannot search with a text search tool..."
"Although it is a low-code solution with a graphical interface, often the error messages that you get are of the type that a developer would be happy with. You get a big stack of red text and Java errors displayed on the screen, and less technical people can get intimidated by that. It can be a bit intimidating to get a wall of red error messages displayed. Other graphical tools that are focused at the power user level provide a much more user-friendly experience in dealing with your exceptions and guiding the user into where they've made the mistake."
"The reporting definitely needs improvement. There are a lot of general, basic features that it doesn't have. A simple feature you would expect a reporting tool to have is the ability to search the repository for a report. It doesn't even have that capability. That's been a feature that we've been asking for since the beginning and it hasn't been implemented yet."
"In terms of the flexibility to deploy in any environment, such as on-premise or in the cloud, we can do the cloud deployment only through virtual machines. We might also be able to work on different environments through Docker or Kubernetes, but we don't have an Azure app or an AWS app for easy deployment to the cloud. We can only do it through virtual machines, which is a problem, but we can manage it. We also work with Databricks because it works with Spark. We can work with clustered servers, and we can easily do the deployment in the cloud. With a right-click, we can deploy Databricks through the app on AWS or Azure cloud."
"Lumada could have more native connectors with other vendors, such as Google BigQuery, Microsoft OneDrive, Jira systems, and Facebook or Instagram. We would like to gather data from modern platforms using Lumada, which is a better approach. As a comparison, if you open Power BI to retrieve data, then you can get data from many vendors with cloud-native connectors, such as Azure, AWS, Google BigQuery, and Athena Redshift. Lumada should have more native connectors to help us and facilitate our job in gathering information from these new modern infrastructures and tools."
"I'm still in the very recent stage concerning Pentaho Data Integration, but it can't really handle what I describe as "extreme data processing" i.e. when there is a huge amount of data to process. That is one area where Pentaho is still lacking."
"A change in the metadata source cripples the whole ETL process, requiring each module to be manually reopened."
"There is connectivity with other databases, however, this is the most significant issue that has to be addressed."
"We In upgrading SSIS, we encountered challenges fixing SQL Server and performance issues, including problems during a failover in our data warehouse."
"Improving the login procedure would make our reporting easier on monitoring our ETL processes."
"Tuning using this solution requires extensive expertise to improve performance."
"We have a stability problem because when something works, it works one time. The next time, it doesn't work."
"I come from a coding background and this tool is graphically based. Sometimes I think it's cumbersome to do mapping graphically. If there was a way to provide a simple script, it would be helpful and make it easier to use."
"There was also not enough instructions from Microsoft in regards to this application or this technology, which can easily be improved upon."
"It's stable, but it depends on the office and location."
"There are issues with certain Apple devices."
More Pentaho Data Integration and Analytics Pricing and Cost Advice →
