Please share with the community what you think needs improvement with Quest SharePlex.
What are its weaknesses? What would you like to see changed in a future version?
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. We have discussed this and they have said it is in their future pipeline, but not with a definite date at which we will see this type of feature.
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. Also, maybe if we could have a seperate section of showing out-of-sync tables in Foglight, instead of looking into the "warning" messages.
The reporting features need improvement. It would be very good for users to have a clear understanding of the status of replication. In the next release, they should add support for integrations between databases to be increased. Currently, you can only transfer between Oracle and SQL, SQL and Oracle. If this was developed more, it would be very, very good.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.