G2

Brian G.

DBA

Mid-Market (51-1000 emp.)

6/23/2020

"Easiest failover software for SQL Server"

5/5

What do you like best about DxEnterprise?

This software makes it incredibly easy to do failover for SQL Server. If you have ever used PolyServe, DxEnterprise offers all of the same features and more. Plus it is a supported tool unlike Polyserve.

DxEnterprise makes it easy to install a new SQL Instance, upgrade an existing SQL instance and failover an instance. On top of that, it will fail over any services you want along with the instance and will move the SAN disk over to the failover machine too.

It is a stable and very useful tool supported by an excellent team at DH2i Review collected by and hosted on G2.com.

What do you dislike about DxEnterprise?

The ONLY feature that I dislike is when I have built a bad template for install and the install fails. The error message it gives back is not that descript and I need to dig into the filesystem to grab a copy of the summary.txt file to figure out what went wrong.

This annoyance is very minor though and exists with SQL Server itself. Review collected by and hosted on G2.com.

Recommendations to others considering DxEnterprise:

If you are looking for a cost effective failover solution for your environment, DxEnterprise is the way to go. It offers support for any windows service to fail over to a secondary (or more) machine. You can even group like services or sql instances together and fail over a group without failing over the entire machine. Review collected by and hosted on G2.com.

What problems is DxEnterprise solving and how is that benefiting you?

The problems that this tool solves are failover. This is a cost effective, cross platform tool for handling failover of SQL instances and, as of the last time I investigated this, is the only tool that offers cross platform failover. What I mean by cross platform failover is you can have your primary SQL instance hosted on a Windows VM and your secondary on a Linux VM and DxEnterprise can fail this over easily. This can help reduce costs of licensing on your Windows VM's.

On top of that, if you need to do maintenance on a SQL instance, failovers take the time it takes for the SQL instance to come online. At my workplace, this is approximately 1 minute on our slowest to start instance. And the instances start up concurrently so the failover takes as long as the slowest to start instance. Due to this, it is possible to do server maintenance (with a minor interruption) during company uptime. Review collected by and hosted on G2.com.