Quest SharePlex Reviews

Our application is hosted in multiple data centers and we primarily use SharePlex for keeping the data replicated from one data center to the other. We use it for business continuity, so that if we run into any issues in the primary data center where the application is currently hosted, with SharePlex we are in a position to switch over to the secondary data center, to do a failover, pretty much in real time.

We have Cisco UCS servers where we have our Oracle Databases running with Linux version 7. These are standalone databases, but I've been a part of a different business unit in our company where we had real application clusters. Right now, it's standalone Oracle 12c and we are migrating to 19c. We have SharePlex replicating Oracle data. It is IoT data so the number of transactions happening is huge. SharePlex keeps the data in sync with the other data center, which has almost the same configuration of the bare-metal servers, Linux, Oracle and SharePlex.

We primarily use SharePlex for the IDBMS, but we have also used SharePlex for Postgres and for Kafka.

Our implementation of SharePlex is entirely on-premises.

We use it for more than high availability and disaster recovery. It keeps the data replicating, live, to our other data center. To a certain extent it provides us with disaster recovery, but we rely heavily on it because if any network or other type of issue happens in the primary data center, due to SharePlex replication being real-time we have the data available almost instantaneously in the other data center. We have the primary data center in the U.S. and the other data center could be in Europe or Asia-Pacific.

In addition to business continuity, which is what we primarily use SharePlex for, it helps us do all our maintenance, when there are both planned and unplanned outages. In general, it helps us avoid any kinds of outages. For planned maintenance, if the entire data center networking infrastructure has to be upgraded, thanks to the SharePlex replication we just fail over the application to the other data center and carry out the maintenance in the primary data center. That maintenance could take hours or even a day. SharePlex seamlessly replicates all the data. There is no data loss and all the backlog data is replicated and posted on all the other data centers within a few hours.

It also enables us to maintain high availability while reducing the related hardware and storage costs.

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 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 have been using Quest SharePlex since 2007.

The product is quite stable and robust. We never run into any out-of-sync issues that happen in our application products. I can hardly remember anything happening for a very long time.

Since I started working here in 2007, we have been through so many upgrades from Oracle 7 to 8, 10, 11, 12, and 19. These are just versions that are compatible with the databases. But we have also had interim SharePlex versions when we found features we would like to avail ourselves of, and it's been very smooth.

It is quite scalable. Support has given us different ways to scale while managing and maintaining databases that are in the terabytes. We haven't had any situations where the scalability of replication became a major issue.

SharePlex is being used extensively in our organization. It's a part of our "DNA," primarily when it comes to high availability of applications and maintenance, because without having real-time data available in the other data center, we wouldn't be able to provide this kind of availability and scalability for our infrastructure and for our customers. 

We are increasing usage. As we are getting more and more customers, we are expanding and are getting more IoT data. As a result, we are doing more and more implementations of SharePlex. It is literally in all our geographies. We have it in our China data centers, we have it in Canada, in the U.S., and Europe. We have it implemented across the world.

We have Premier Support. As a result, any type of support case we submit is looked into almost instantaneously. We can call the support number, and if it's a severity-one case, we literally have someone working with us in a few minutes.

Premier Support from Quest was one of the clinching benefits at the time we evaluated GoldenGate. It was one of the things that all the DBAs, unanimously, were really feeling great about. It meant not having to go through the support that Oracle has for GoldenGate. Since most of our DBAs are quite experienced, whenever we create a case we have literally exhausted all the options that we could, as senior people who have been using replication. SharePlex support understands that whenever we create a case, it's really a genuine issue and they literally jump onto a WebEx session with us instantly. Premier Support is absolutely fantastic.

The Premier Support also adds overall value to our investment with Quest. They have escalation. Whenever we spend a few minutes with them and they realize that an issue is something that needs escalation, they are quick in getting a senior support person on the WebEx session, helping us out, and providing a solution. We have had their support during the night, at times, working in the USA, trying to help understand all the issues and apply the solutions.

SharePlex was already working here when I started with the company. We did use a little bit of Oracle Streams, which was, of course, before Oracle acquired GoldenGate. We tried to use Streams and we ran into a lot of issues with it. We were looking at it as an alternative, to see if it had any additional features. But we continued to like the simplicity and scalability and support that we had with SharePlex.

It is a very simple installation, right from setting up new databases between two data centers and setting up replication, to configuring it. We have database releases happening all the time, every few weeks. The initial configuration, such as adding new tables to replication, is very simple and straightforward. 

Deployment takes a few minutes, because I've been working with it for a while. For someone who has not worked with replication products, it might take a bit of time. But I did a proof of concept of GoldenGate and, when we did the compare and contrast, SharePlex was still very simple to install and configure and upgrade.

In terms of implementation, having the right file system helps. We use NFS. And we are a NetApp shop so we use NetApp for SharePlex. Having the right kinds of permissions for the NetApp file systems is also important, and they are well documented in the SharePlex Knowledge Base.

Installing it is very simple. Anybody who understands English and databases would be able to follow a few prompts and install the software. Adding tables for replication is also very simple. You have the source database name, you know the target database name, and you know the Oracle tables to be replicated. That's about it.

Deploying just requires a DBA, and we have terabytes of data being managed and replicated within Oracle databases using SharePlex. One of the biggest databases is 80 to 100 terabytes. For maintenance of SharePlex, in the business unit I'm part of, we have 100 or so databases, and each database has five to seven SharePlex bots that are replicating data to the other side. We have three people in the U.S. who manage and maintain it. We also have four or five people in India, but we do most of the installation, configuration, and upgrades in the U.S. We find it very smooth, without any hiccups. All the people managing are Oracle, SQL, and NoSQL DBAs. It's the DBAs who manage the production, development, and QA environments.

We have so much in-house expertise that we have not needed third-party assistance. Everybody here has been working for at least three to five years. That solid knowledge base of our own helps any newcomer. We can go over it in a few hours and get them up to speed.

We have absolutely seen return on investment from using SharePlex. We have never run into any issues when we have had to fail over our applications to another data center. There has never been an issue with data not being available. That, itself, has been ROI. In addition, for any network issues or any user-related errors that have happened, we have seen a tremendous return on investment.

It's really good value for the money. There are some things they could improve on, but in terms of the pricing, features, and support, as a holistic package, we are not thinking of anything else at this point in time.

We really haven't evaluated anything other than GoldenGate, which was evaluated a few years back. The licensing cost and the support are what kept SharePlex our chosen product.

We really didn't go beyond the proof of concept with GoldenGate, so I can't comment on its performance. We didn't go into production with GoldenGate. But the factors that really made us retain Quest were the simple installation and configuration. We could be a little biased because we have been using the product for a while, but most of the DBAs agreed that GoldenGate was more complex to set up.

And the licensing of GoldenGate was expensive—two to three times more expensive than SharePlex. 

And when it came to support, we didn't get any indication from Oracle that we could have a different level of support when we ran into issues, such as getting someone really quickly on a WebEx session to go at an issue.

It's very simple to use and to install and the support they provide helps with the return on investment. It helps you achieve high availability for your applications.

We haven't used SharePlex for upgrades and migrations simply because, having replicated the data to our other data center, we can bring down the data center where we want to do the upgrade or the migration, and have the data backlogged in the other data center. When we are done with the upgrade, we just get the data posted, in SharePlex terms.

I would highly recommend SharePlex for beginners or even for people who are evaluating other products or doing proofs of concept. Try it out in your production and you won't be disappointed. It just works. Install it and forget about it.

We use Quest SharePlex for a specific reason. We are migrating from on-premise to cloud.

SharePlex is a replication service. We are using it to do the migration of our databases to AWS Cloud. Once everything is migrated, then we won't be using the solution.

We have small to very large databases in terms of size. We were looking at a solution where we could cut down the migration window. We wanted to cut down the outage window and reduce the overall cost of migration to the cloud. For example, if there was a very large amount of data, e.g., five or 10 terabytes, and we were trying to migrate that database over a weekend, then that it is a risky proposition. We were looking for a solution where we could do a migration before the cutover time, then keep it in sync. So, when we were at a point when we were ready to switch, then we could just stop the replication and bring everything up in the cloud. That was our main use case for using SharePlex.

We started on version 9.2. Now, we are on version 10.

Our primary goal was to reduce the cutover time since we are dealing with hundreds of databases for our migration. Using Shareplex helped us to achieve that goal. It was an important variable because it helped us reduce our risks during migration and resource time and efforts. We were able to do most of the validation checks before and during the migration which helped us a lot to mitigate risks and reduce cost and time.

The most valuable feature is the replication feature, since we are dealing with multiple projects at the same time. We are migrating close to 25 to 30 projects. If I just count the number of environments, it turns into probably 200 databases (more than 100 from the production environment).

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 SharePlex 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.

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.

We have been using SharePlex for the last year, including the time we spend in PoC. Actively, we have been using it for the last nine months.

The stability has been pretty good, except for a couple of instances where we had to do the migration again due to some issues with the initial setup and migration. Whatever failures or issues we had, we were able to resolve them. It is a stable product.

Scalability wasn't really something that we tested for, since we have been using it mostly with one-to-one relations, i.e., one target for one source.

Technical support has been very helpful overall. 

Whatever root cause analysis we have done was mainly on the SharePlex side. For that, we have pretty much worked with their support engineers. Since we are a Premier customer, we have always gotten a very good response from SharePlex support.

There have been some critical moments where the Premier support has provided valuable insight when resolving some issues that were critical to the project's success.

We did not previously use a different solution.

When we cease to use SharePlex, we will also stop using Foglight because we usually use OEM for the Oracle Database management and haven't really explored Foglight for database monitoring purposes. So, we will probably continue with that for database monitoring.

Since we had multiple scenarios to test out, it took us a few months to test out all our use cases. It was a long process. However, with the help of Quest support, we completed our PoC. It was a long process because we wanted to test all the scenarios.

Our main goal was to have seamless replication that could help us with smooth turnover. 

We did not use a third-party integrator to assist us with the implementation. We handled the process ourselves.

During the PoC, we had someone guide us through all the use cases for the process. That took two to three months.

The ROI will come from us being 100 percent in the cloud by the end of June this year. This was a necessary deadline, and we will meet it. Therefore, the product was worth it in our books.

It is not as expensive as Oracle GoldenGate and has worked really well within our budgets.

Previously, we did look at AWS DMS service, which is a data migration service. Whatever tests we did there, we were not really satisfied with the overall results. We found out that DMS doesn't handle LOB column migrations very well. It also isn't really that stable and recovering from failures wasn't that straightforward. Those were the two biggest factors that made us move away.

SharePlex provides real-time activity screens. You need to install a separate tool for this, which is also provided by Quest called Foglight. These solutions work well together. Right now, we are using Foglight only for SharePlex monitoring. The Foglight interface is pretty neat. Whatever presentations I have given to my management, they have been pretty impressed by its GUI. It gives a pretty cool description and display of your replication status.

SharePlex has been a good fit for us because it was not as expensive compared to GoldenGate. It was also stable compared to AWS DMS. It was a good product for what we were looking for and within our budget too. Overall, we have been satisfied with this product. There is no reason not to use it.

I would rate the solution at a nine out of 10.

We use SharePlex to migrate and update from one data center to another. It's helpful for DR and broadcasting solutions. The main use case is to minimize downtime for migration or upgrade. The second objective is real-time replication. The main SharePlex users are database administrators. We're the replication administrators in the company, and that's the primary user base.

We've used it to upgrade from Oracle 12.1 to 12.2 and Oracle 12.2 to 19c. We've also done cross-platform upgrades and migrations from on-premises to the cloud. 

I would rate SharePlex's high availability, and disaster recovery features highly. It works as advertised in terms of rapid fill-over and switch-over opportunities. It reduces the migration time for a multi-terabyte database to an hour or less because it performs real-time replication. SharePlex reduces downtime and migration time exponentially. Something that could take 12 to 24 hours is cut down to one to two hours.

By the time you start to migrate, the only remaining replication is a slight difference in data from the point when SharePlex has shut down, and the application has to also switch over to the new database.

It allowed the company to replicate data more transparently. Some of the business executives probably don't even know it's there. It works 100 percent of the time, with little downtime or problems. It provides what is needed. There's little concern about whether or not it functions. 

It's allowed the company to achieve its objectives with its clients, reducing and minimizing downtime for substantial migrations and upgrades. It can reduce hardware and storage costs, but my company doesn't utilize it with high-availability architecture.

I like SharePlex's Compare and Repair tool. 

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.

We've been using SharePlex for about eight years.

Any logical replication solution can become complicated when you have a large system with multiple databases that have to have HA and DR on the architecture. The more components you have, the more SharePlex services you need. That can become complicated to manage only because of the way logical replication works. It's not necessarily a SharePlex issue. It's a logical application issue.

We have a Premier Support contract with Quest. Their response times are excellent, and they stay on an SR until it's resolved. Their technical support is a cut above other vendors I've used. They stand out because they will do whatever they need to assist you, whether it's by phone or a video chat. They'll do what they need to stay in contact with you.

We used Oracle Streams but switched because Oracle stopped supporting the product a decade ago. We needed a solution that was mature and usable. 

Setting up SharePlex is straightforward. A user has to provide probably fewer than 10 questions or input values, and the configuration is similar.

Generally, we need to do at least one round of testing the product in a non-production environment. We provide feedback to management, and the executives will ultimately approve the implementation. Finally, we deploy it on Open Linux systems with Oracle. 

Initially, we used Quest contract services with some of our larger projects and used their hours to support the new system.

It's worth your time to take a hard look at pricing and compare costs but you should also consider the simplicity for any administrator who is new to replication.

We evaluated GoldenGate. The cost was a deciding factor. Also, SharePlex was easier to set up, and the learning curve was also much shorter. Oracle's replication solution is comparable to SharePlex performance-wise, but SharePlex is more cost-effective. 

I rate Quest SharePlex nine out of ten. SharePlex is a mature product now, but it is highly versatile. It can reach a broader platform and database market than it does now. And I think that's probably what Quest is working on.

My biggest lesson is that you can find ways to simplify areas of a product to achieve market value. Even something complex like a logical application can be simplified for administrators.