Oracle Data Guard Reviews

The Active Data Guard and Fast-Start Failover features are excellent. The Active Data Guard helps in providing read only data for reporting purposes. The Fast-Start Failover is an automatic feature that allows failover from primary database instance/server to the preferred standby instance/server.

I've implemented these features in several projects.

Oracle Data Guard is part of the Oracle Database Enterprise Edition. Oracle Corporation has provided features in Data Guard for its new Database version Oracle 12c.

I've used Oracle Data Guard for over eight years.

Yes, If the underlying Network is not stable, then the Data Guard and Standby Databases will disconnect and not be operational.

No.

Oracle Support is rated an eight out of 10.

If the Database SLA is much higher than Oracle RAC, it is a better product than Data Guard.

The initial setup was simple, but there were problems setting up the connectivity between the different servers. Once these problems are resolved, then the Data Guard was operational.

The Oracle Data Guard is part of the Oracle Database Enterprise Edition, there is no extra licensing cost for the software. However, there is a hardware cost for the number of Standby Databases for each server and storage.

The only other product is Oracle RAC which is very expensive for small businesses as it involves software for clustering, hardware for networking and larger SAN environments.

It's a simple replication solution for small businesses.

Provides an active data guard.

I would like to see better failover.

We have been using this solution for five years.

There were no scalability issues.

I would give customer service a rating of 7/10.

I would give technical support a rating of 7/10.

We did not evaluate another solution.

We did not implement through a vendor team.

We did not evaluate other options.

This is one of the most stable products to support critical DR sites.

It provides us with online replication.

I would like to see replication/fail-over sites.

We have been using this for over five years.

There were not many deployment issues.

There were not many stability issues.

We sometimes had scalability issues with read only.

I would give customer service a rating of 8/10.

I would give technical support a rating of 7/10.

There were no previous solutions.

It was a self-driven setup. It was not too much trouble.

We implemented in-house.

We are under ULA.

We did not evaluate many other solutions.

It simply works.

We use it for backing up our data, so from the standby instance.

Data Guard has been around for a very long time and a lot of big companies are using it. I don't see that it needs any improvement or anything like that. I think it's pretty solid.

I've been using it for more than 15 years.

We've experienced no issues with performance.

When you open up SR Oracle has a list of things which they ask for. Being an end customer, when we open SR, we give as much as information as we want and again the support person comes into the picture, and without reading what we have put through, they just has the same question over and over. What version, what product, all that kind of things, which is not at all fair.

It’s the backbone. Nobody interacts with it, it's only the DBAs who use it I think. Once you set it up it's pretty much done. You don't deal with it on a daily basis.

Maybe not all products are up to the speed or like any product you take, there is space to improve. I think for our company, the way we use it, we are very happy with it and the end customer is very happy with it.

I have found its switchover functionality to be most useful using which you can perform disaster recovery within no time. Its feature of FAL is also pretty useful that helps to keep both sites (primary and standby) synchronized. Logical standby database is also a pretty handy feature for reporting purposes.

Active Data Guard has helped us a lot in achieving the real time reporting by offloading our heavy reports from Production to Standby database. 

Limited functionality to exclude any schema/table from replication would be helpful.

Currently Data Guard replicates whatever DML operation is performed on primary database is replicated to standby database as it is. To improve it bit further, if Oracle can provide some kind of feature in which user can select any schema or 5-10 collection to tables in some schema that user doesn't want to replicate. Because this kind of feature is available in Oracle Golden Gate which a separate licensed product with a lot of features like that one that I mentioned for limited replication, heterogeneous replication, cross database replication.

I use Oracle Data Guard as a DR (disaster recovery) solution. Usually, I use the free license Data Guard, which is called the physical Data Guard.

Oracle Data Guard has a nice feature called the DataGuard snapshot to open the solution in the read-write mode and make some changes to the database. When you finish your work, you can do a rollback to the point that you started the snapshot and continue working.

Sometimes, the technical support team takes time to respond.

I have been using Oracle Data Guard for ten years.

I rate Oracle Data Guard a nine out of ten for stability.

I rate Oracle Data Guard a nine out of ten for scalability.

Sometimes, the technical support team responds quickly; other times, they take time to respond. Usually, the first response or action from the Oracle site on my service request is rapid.

The solution’s initial setup is straightforward.

The solution's deployment time may vary according to factors like the database, storage, size, network facilities, and security. On average, the deployment takes three days.

Oracle Data Guard provides DR and acts as a high-availability solution in case of a crisis in the primary database.

Overall, I rate Oracle Data Guard a nine out of ten.

The deployment cost is expensive. 

I have been using the product for ten years. 

Oracle Data Guard is scalable. I rate it a ten out of ten.