We performed a comparison between Informatica PowerExchange, Quest SharePlex, and SSIS based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."Mainstream integration and real-time integration are the best features."
"It is easy to integrate the solution with other tools."
"The product's initial setup phase was not complex. The tool is easy to install onto any of the servers, and you can integrate it."
"The most valuable feature is connectivity to data sources."
"The scalability is excellent."
"Provides a significant amount of control over the landscape and overall implementation."
"The user interface and user experience are perfectly all right."
"The transformation work called for Informatica PowerExchange. It was easy to work with this and very stable."
"The core replication and its performance. Performance is crucial, and SharePlex is by far the fastest. The way it handles replication to multiple targets along with basic filtering, as well as from multiple sources to a single target, is very efficient."
"I like SharePlex's Compare and Repair tool."
"There are some capabilities within SharePlex where you can see how the data is migrating and if it still maintains good data integrity. For example, if there are some tables that get out of sync, there are ways to find them and fix the problem on the spot. Since these are very common issues, we can easily fix these types of problems using utilities, like compare and repair. So, if you find something is out of sync, then you can just repair that table. It basically syncs that table from source to target to see if there are any differences. It will then replicate those differences to the target."
"The core features of the solution we like are the reliability of the data transfer and the accuracy of data read and write. The stability of the solution is also excellent."
"Because of the volume of the transactions, we heavily use a feature that allows SharePlex to replicate thousands of transactions. It's called PEP, Post Enhancement Performance, and that has helped us scale tremendously."
"The most valuable feature of SSIS is its ease of use. It is easier to use than other applications."
"The script component is very powerful, things that you cannot normally do, is feasible through C#."
"It is also easy to learn and user-friendly. Microsoft is also good in terms of technical support. They have built a large community all over the world."
"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."
"SSIS is easy to use."
"I have found its most valuable features to be its package management capabilities and the flexibility it offers in designing workflows."
"It is easily scheduled and integrates well with SQL Server and SQL Server Agent jobs."
"The most valuable aspect of this solution is that it is simple to use and it offers a flexible custom script task."
"They should make it quick and easy for use of citizen data integration or for people or integrators developing at the customer side. They could be development teams within the business team. For them, the product owners can consider making it a little bit more seamless and a little bit more democratized."
"The connectivity with T24 core banking could be improved."
"I would like the stability to improve."
"Integration with the largest number of databases and other systems would be important."
"V10.2 is very stable, but we are still struggling to make V10.5 stable. We found services that were down, and PowerExchange stopped working."
"Technical support can be improved with respect to delays in ticket response time."
"Apache Spark has a machine learning algorithm, an area where Informatica PowerExchange lacks."
"The solution could be made more user-friendly. The configurations are also quite difficult."
"For its function in relation to replication (i.e. filtering), I'd give it a six or seven out of 10. GoldenGate has much more functionality by comparison."
"I don't know how easy it would be to change the architecture in an already implemented replication. For example, if we have a certain way of architecting for a particular database migration and want to change that during a period of time, is that an easy or difficult change? There was a need for us to change the architecture in-between the migration, but we didn't do it. We thought, "This is possibly complicated. Let's not change it in the middle because we were approaching our cutover date." That was one thing that we should have checked with support about for training."
"I would like more ability to automate installation and configuration in line with some of the DevOps processes that are more mature in the market. That would be a considerable improvement."
"I would like the solution to have some kind of machine learning and AI capabilities. Often, if we want to improve the performance of posting, we have to bump up a parameter. That means we need to stop the process, come up with a figure that we want to bump the parameter up to, and then start SharePlex. Machine learning and AI capabilities for these kinds of improvement would tremendously help boost productivity for us."
"The reporting features need improvement. It would be very good for users to have a clear understanding of the status of replication."
"The performance of this solution is not as good as other tools in the market."
"There is connectivity with other databases, however, this is the most significant issue that has to be addressed."
"The high prices attached to the product can be an area of concern where improvements are required."
"SSIS sometimes hangs, and there are some problems with servers going down after they've been patched."
"The solution should work on the GPU, graphical processing unit. There should also be piping integration available."
"Video training would be a helpful addition."
"Future releases should improve the data lineage, as it currently is not good."
"Improvement as per customer requirements."
