We performed a comparison between BMC Data Management for IMS and DB2 on zOS, IDERA ER/Studio, and Quest SharePlex based on real PeerSpot user reviews.
Find out what your peers are saying about Oracle, Quest Software, SolarWinds and others in Database Development and Management."BMC Data Management improved our data recovery process by simplifying it."
"I have worked with DB2's great features in the last five years. The IDAA feature transformed the vision of warehousing, business analytics, and big data at my bank. Besides the mainframe, I saw that this solution was evolutionary. It gives real-time information."
"Using this product has improved the way we maintain our models because they have a place where we can keep all of them, and they can be viewed using the web interface."
"We can track changes to our data models and tie those changes back to specific tasks or efforts that we identify."
"The data modeling and reverse engineering features are most important to us."
"When validating the model, the ability to provide sub-models to developers, and generate a physical model from the logical, makes it easier to review a logical model with stakeholders."
"It does the job."
"The most important features are logical and physical models that we can compare and develop. Also, the Data Dictionary can be created out of your studio. Finally, database schemas help understand the logic that's behind the scene, behind the SQL tables. Especially when there are a lot of them, the schemas help everyone understand the business processes."
"We found a lot of duplication, a lot of non-conformity in the way our databases were designed. By identifying these situations, we're able to go back in and try to create a more standardized solution."
"This application does a lot of things, as do competitor products, but the main reason to go with this product was the ability to create many automations, where we can improve our work and our process."
"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."
"I like SharePlex's Compare and Repair tool."
"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."
"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."
"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."
"DB2 is a hard tool to grasp. It's hard for users to learn how to use it. It's not easy to see how it works."
"One area for improvement with this product could be in providing clearer guidance and tools for disaster recovery planning and execution."
"We would always like to see Repository performance improve, checking in and checking out."
"I'd like the ability to debug the errors ourselves instead of having to call them. There are certain types of errors that, I wouldn't say they come up regularly, but when you have an error it is very often the same type of error. Knowing that it's a Type III or Type I, it would be nice to have some kind of debugging facility for us to use to find out where the problem that threw that error occurs. That would be a really cool feature."
"They allow functionalities to be released before the full tests for catching and correcting errors are completed."
"The only thing I had an issue with was licensing, and the support was very good."
"when there are some links to the external databases, if this database is not structured it is not uploaded. It gives me errors and I cannot see the view that was created on this structure and I cannot change those views, even manually. It skips the views. I have to ignore those views. I cannot re-upload them because it gives me an error."
"When building the relationships there should be a little more flexibility."
"I would like to see better documentation/help for the Data Architect tool. Creation of tutorials would be nice, as there are some features which are not as clearly defined as they should be."
"What needs the most improvement are semantic lineage and usability."
"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."
"The reporting features need improvement. It would be very good for users to have a clear understanding of the status of replication."
"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."
"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."
