Nutanix Database Service Reviews

We are a service provider for Nutanix using a cloud platform to deliver Database as a Service to our customers to compete with AWS and RDS.

We deliver databases as a service, so the Nutanix Database Service makes scaling and deployment simpler and more agile for our customers. It has reduced the time needed to provision a database by 40 percent. 

The ability of Nutanix Database Service to automate database admin tasks has helped lower the cost of DBA operation through a simple and efficient deployment. Lower personnel costs mean lower operational costs of services and support. We also make a passive income with this product, so it affects us positively. 

I like how easy it is to implement MySQL, SQL, and open-source database platforms.  Our developers use Nutanix Database Service to refresh databases directly from their development environments. For instance, we can upload more than 500 databases with just twice the CPU load. 

We use MariaDB enterprise versions. It has simplified our work and enabled us to deploy customers who use these solutions.

It would be helpful if Nutanix added a billing system for databases. We need to automate this with a separate solution. We are service providers, so it would be easier for our customers if there were a built-in system that we could use for billing.

We have used Nutanix Database Service for two years.

Nutanix Database Service is stable.

Nutanix Database Service is scalable.

I rate Nutanix support nine out of 10.

Positive

We have been Nutanix customers for eight years. It was a simple procedure since we have used Nutanix services for so long. We didn't use any specific strategy for deployment or any third party.

We make passive income using the Nutanix Database Service, so the financial return was very good for us.

I rate Nutanix Database Service nine out of 10. It isn't perfect and still requires some development. 

Nutanix Era is used for multiple databases where there are a lot of compliance requirements, including backdated restore points for applications. This is particularly useful when the application team needs to be restored quickly. In normal scenarios, this setup would take a day. With Era, it takes minutes. Additionally, the solution simplifies the deployment of various supported databases for UAT service, easing the workload for infrastructure and database teams.

Nutanix Era significantly reduces operational overheads for the IT infrastructure team, backup team, and application team.

Nutanix Era effectively reduces operational overheads by streamlining the application team's implementation of multiple environments. The solution provides databases for audit or analytics services, which are crucial in operations. It supports fast database cloning, enabling quick responses from the application team for product launches without accessing production databases. Proper use reduces errors from infrastructure teams and improves time to market efficiently.

Era should be compatible with various environments, such as VMware and Red Hat, to be hypervisor agnostic. Due to increasing adoption among enterprise clients, integration with Kubernetes platforms is also needed. Furthermore, the product can benefit from improving its understanding of architectural setup and communicating its limitations to users and partners.

I have been working with Nutanix Era for more than four years.

With Nutanix on-premise, I rate the stability as eight out of ten. However, for hybrid platforms, I would rate it lower due to limited functionality.

Scalability is an inherent function of Nutanix Era and works well both on-cloud and on-premise, deserving a high mark.

Technical support from Nutanix has room for improvement. There seems to be a lack of understanding of system limitations and architectural specifics, resulting in deployment challenges.

Neutral

The initial setup of Nutanix Era is straightforward, maintaining Nutanix's reputation for simplicity and ease of installation.

The pricing for Nutanix products is on the higher side, and more flexibility in the licensing model, such as a GB-based license, would likely increase adoption.

I rate Nutanix Era five out of ten. The core-based licensing model is restrictive, and I would recommend that consideration is given to use-case-based license models to improve adoption. I have recommended Nutanix Era to others after increasing awareness of its functional limitations and support challenges.

Our main requirement was to simplify our database operations and management. We have a large number of databases and we have DBA teams that support and provision databases. The idea was to look into a database as a service. Similar to their offerings in AWS and Azure, where you can provision based on your requirements, and automatically everything will be handled by the platform, reducing human errors and waiting times. This is why we looked at Nutanix.

The time to provision the database went from taking a couple of days to now taking a few minutes. That is the immediate impact we saw. It helped the team to focus more. They can now be focused on support rather than spending time provisioning, which is a repetitive activity.

Additionally, one of the features we really like is the patch management. Patch management was always a challenge for us because we had to schedule. We have to manually apply the patch, and there is a process for it. Now with NDB, this is all automated. There are hotfixes that automatically get applied, there are other major updates that are all managed by NDB. It reduces the team's effort. They can now focus more on fine-tuning and improving the database we have.

We are saving around eighty percent of the time spent on provisioning and recovery with this product. 

Another benefit is the recovery. That's one of the features that I like a lot. It gives us the capability to recover data within minutes. It has a time machine similar to Mac's time machine. You can go back in time and recover your data almost immediately. The traditional way of doing backup and restore usually takes hours and you will have to restore the whole database tool to recover only a little bit of data.

Nutanix helped automate database admin tasks like provisioning, recovery, and patching.

With the ease of provisioning, Nutanix has really helped to expand and fast-track the provisioning of the applications.

There will always be room for improvement, there is nothing perfect from day one. There are some technical challenges that we have with NDS. I believe with time it will be sorted out. 

They focus more on increasing performance and resiliency. They make your normal databases as a managed Service, like SQL, and Oracle Database and I believe there could be improvements for resiliency and high availability technologies. They could seamlessly provide that for those databases. 

I have been using Nutanix Database Service for three to four years. 

Stability is excellent.

Scalability is built into the platform, it's excellent. 

They have a very good response time. Engineers that connect to support are experienced and knowledgeable compared to other vendors.

Positive

We see ROI in the automation that saves admin time. 

It's a little expensive. They should reduce the price if they want a bigger customer base. 

I've seen something similar to NDB from the AWS and Azure offerings in the cloud. We wanted something on-prem. We went with Nutanix because we're a bank. We need data resiliency in our data center as part of our compliance.

I would rate Nutanix Database Service a nine out of ten. 

We used to use Oracle ODA and it was difficult to provide test and development database snapshots for the whole Dev team. It's easier with Nutanix. We switched to Nutanix because of its scalability and simplicity. 

Oracle is fantastic but it's really difficult to deploy. With Nutanix, I can deploy an image and I can replicate it to my Dev team. All of my servers have the same CPU, RAM, disk, and cloning. Nutanix is much easier than Linux or Oracle ODA. 

Snapshots take up a lot of disk space in Oracle. My team and I really like that Nutanix duplicates the size of the snapshot.

My organization has improved with Nutanix because now, the Dev team can use CI/CD. Before, it was a monolith application and now Dev cut the application into microservices and began to deploy with continuous implementation, continuous development, and quality assurance. This was impossible with Oracle ODA, it was a monolithic application.

The API and monitoring features are good. Nutanix is good for my use case. I don't see the need for it to improve.

Our developers use Nutanix to provision and refresh databases directly from their development environments. It affects developer productivity. They're a lot faster. They can create all Dev databases on demand. When they want something, they execute the code and they have the environment, clean, fresh, and usable.

With Oracle, it took around one hour to refresh the database and now, with Nutanix, it takes a quarter of that time. 

Nutanix has helped to automate tasks. I schedule a refresh for a clone every morning for the team for troubleshooting purposes. 

It has simplified my life. It simplified tasks. 

I can check the status of my database from my monitoring tool, the report teams can refresh the database with API, and close the database with API. It's very useful and powerful.

I have been using Nutanix Database for two to three years. 

Their support is great. 

It's expensive but it's a good price. We have a regular license program because it's really expensive. 

We run Nutanix on HPE hardware because Oracle is only one vendor with one CPU. Oracle's licensing model is a CPU model and Nutanix's hardware is multiple CPUs. 

I would rate the solution a ten out of ten. 

The primary use cases for our clients are storage and data management.

What I like about this solution is that it's more reliable compared to other solutions.

The downside of this solution is that it's more expensive than its competitors. 

The other thing is that the scalability part of this solution should be improved.

I have been working with this solution for about four years.

I would rate the scalability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the technical support of this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.

Neutral

My impression is that the initial setup process is a bit complicated but manageable. It's a good product and it's easy to manage. The deployment time depends on the amount of data the client is gonna be storing. 

Usually, it will take one or two people to carry out the deployment.

I would rate this setup process an eight, on a scale from one to 10, with one being the worst and 10 being the best.

My impression is that this solution is really expensive. The licensing is based on a yearly basis since a monthly basis is hard to maintain.

Overall, I would rate this solution an eight, on a scale from one o 10, with one being the worst and 10 being the best.

We propose this solution to our customers to integrate part of their databases into Nutanix Database Service to manage and provision the database.

Management and provision are the most important features of Nutanix Database Service.

The solution can increase its database compatibility and backup options.

I have been using Nutanix Database Service for one year.

Nutanix Database Service is a stable solution.

I rate the solution’s stability ten out of ten.

Our customers for Nutanix Database Service are small and medium-sized businesses.

The solution can be deployed in two days.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten.

My customers don't use the solution's automation features. DB as a service solution is new to my customers, who don't know the solution. Our goal is to increase the knowledge of our customers.

I would recommend the solution to other users because it's a new solution that has more functionalities. It's similar to a cloud solution but can be deployed on-premises or in the cloud according to the customer's needs. With this solution, the customer can recreate a cloud environment in their private cloud, and it's really interesting.

Overall, I rate the solution a nine out of ten.

At my company, I use Nutanix Database Service to set up and version machines, install and configure precomputed machines, and establish connections between databases and application services.

The most valuable features of Nutanix are its robust infrastructure management tools, including a powerful firewall, analytics for system performance, and convenient automation. 

There is room for improvement in the pricing structure, especially given the complexity of our business model involving multiple data centers and a variety of services. While the user-friendly GUI and branded plug-ins for HPI solutions make management easier, there is still a need for simpler operational tasks.

I have been using Nutanix Database Service for two years.

Nutanix's stability is excellent. It has consistently performed well over time, supporting multiple operating systems without any significant issues. It aligns smoothly with our company's varied use cases. I would rate the stability as an eight out of ten.

I would rate the scalability as an eight out of ten.

My experience with Nutanix technical support has been great Whenever I have contacted them directly, there have been no issues, and the support provided regarding mechanics has been very effective. I would rate the support as a nine out of ten.

Positive

I have worked with various products from different vendors before Nutanix, including Cisco's UCS, IBM's Internet, and HPE servers. When choosing Nutanix over other solutions, the decision was based on the HCI features, especially for edge computing with one to three nodes.

The initial setup was incredibly quick and straightforward. It took just a matter of minutes to deploy and prepare Nutanix for usage.

Overall, I would rate Nutanix Database Service as an eight out of ten.

We ran testing for Microsoft SQL and MySQL. For Microsoft SQL, the test case was to do multiple database schema deployments on a single host. Then we had single database schemas on multiple hosts, and we also tested high availability clusters for Microsoft SQL on four host nodes.

The performance and flexibility of non-Nutanix workloads are quite good because from a working perspective or a load perspective, scaling of the system is very straightforward. Since we're running the hosts on the normal Nutanix infrastructure, we were able to scale the loads according to what we need and it's really easy to scale up or down as needed.

The big advantage that we found was because we run development processes as well, we can actually generate development, testing, and production databases on the fly without us influencing production. This is one of the big time-saves because, in the past, you would normally have to take a backup of production, sanitize the data, then put it on a test machine. This is something that Nutanix Era makes very simple to do.

This solution has helped to save us on Tier 1 storage, which is important to us because we do a lot of systems in-house. Storage clusters are quite heavily used and they have a large footprint. Being able to save storage space for non-production tasks is significant because, for testing, we have a group of five testers working there. On dev, we have two or three developers that would work there constantly. Saving on that storage means that we can grow our production environments more effectively because we don't have to pay for test and dev storage separately. This means that the cost of ownership is a lot less, which saves us on having to purchase more storage as the system starts crowding.

If you think about it, if we run dev, test, and production all with production data, because that's what they need to do the development and testing on, we would need three times the data every time we deploy it. If the system then grows to two terabytes, that's six terabytes that we have to pay for. With Nutanix, we basically save four terabytes, which is a lot of money.

We have been able to simplify database deployment across multiple database engines. We tested with MySQL and Microsoft SQL. With MySQL, you can also use the APIs to automate that type of deployment. We have not tested the Oracle or the PostgreSQL deployment engines since we don't have those. However, with respect to the two that we tested, it simplifies them both to a large extent.

Using this solution has made the task of cloning databases much simpler and much faster. Previously, it would take us two to two and a half hours to do a clone or a snapshot. Now it's five, six minutes. It's a lot of time that we save.

We have tested the backup and in-place restore of databases but we haven't finally signed off. Once we complete the pilot, we hope to sign off on those. What we did see is that the way Nutanix Era works with the Microsoft backup system is much easier, and it appears to be more stable. This is mainly because on the Microsoft backup side, if you have a load issue, your backups will normally fail. With Nutanix Era, the backup system sits separately from the performance of the database. This means that even if you have a load issue on the data database system, the backups will still go through. Specifically, this is because Era backs up from the storage device and not from the Microsoft database. It is very technical, but as I understand it, the backup will still go through, even if the database is under strain.

We expect that once this system is in production, it will reduce downtime. One of the main selling points for us was that it will reduce update and patching downtime because it manages those updates and patches internally. Even if you deploy Microsoft SQL patches, you can manage and maintain them from the Prism interface, which should reduce downtime. They save the users downtime, and we haven't actually seen that yet, but we expect the pilot will show us that.

We tested the ability to make multiple backups per day and assess the impact that it would have on our workloads. In fact, we were able to make differential backups continuously without affecting the performance of the database engine. We were also able to schedule the backups at different times to make full backups and we couldn't see any impact or load on the database performance while we were doing this.

This will definitely help to limit data loss because we can use a continuous differential backup. We should not see any data loss as long as there's no data corruption. But if there's data corruption, and we can pinpoint the point in time, we should be able to go back to that point.

The ability to do this is very important for us. We have a series of data profiles that we have databases for. We are a university and our systems include everything from financial systems right through to medical systems that they use for the academic hospitals and the veterinary hospital.

When it comes to data management, I can see how Era will help to reduce the time spent on operational database workloads. Since we haven't used it in production for an extended period, I can't really say how much time we've actually saved. During the PoC, we only played around with it and we set up the scheduled tasks that we normally do manually.

Since we can automate a lot of things, we can skip it and schedule it. This should replace a lot of our off-hours work such as patching, upgrades, and similar tasks that can be scheduled so that the reboots can happen automatically. We don't have to sit there and babysit the whole time.

This product has helped us to reduce our database footprint because it gives us the ability to deploy Microsoft SQL instances as MySQL instances on the same host, without actually having to reconfigure or do anything. This means that we can consolidate our database service.

We can also scale them the way we need them and we can, if we really want to, move away from the one database per server type of instances that we have now into a more economical database model where we have multiple database instances on a single host, which does reduce our footprint quite a lot.

At this time, when we provision a database, we do so for a specific server. We assign the memory, CPU, and storage for that specific machine. For about 50% of the lifetime of that database, those resources are never actually utilized, whereas with Era, we can provision those as instances on the same host, and we can scale the host to cater to all of those. This gives us the opportunity to better manage how many resources are sitting idle because we can ramp them up and scale them back as needed, which will save in the long run.

More generally, using this solution will definitely improve the service delivery for our department within the organization. It's going to make it possible for us to cater to more user-centric services and needs. Because of the time-saving and the resource-saving, we'll be able to provide our users with a bigger variety of database services that they might require.

One feature that is very good is the backup and validation process that's built into Era. It saves a lot of time and gives you some kind of assurance that when you actually pull a backup, it is done correctly and you will be able to restore it. In other backup systems, because they are not database-aware, that validation process is not as easy because you have to actually restore the backup to see that it worked. With Era, it actually validates on the fly so you know you'll be able to restore.

The deployment process is a lot easier, due to the fact that with Era you can actually script a deployment. If you have a lot of deployments of the same type, say for instance you have a user request coming in to say they need a basic database schema, you can just run that as a deploy script and it automatically sets up everything. It takes about five minutes and the users have access to their database. In the past, we had to go through a whole setup and deployment process, which for us, took about half a day. That's a lot of time that we save.

Setting up a development test and production environment is quite easy and it saves a lot of storage because the dev and test databases are non-data clones of production, where only the changes are saved. For example, if you have a two-terabyte production database then it saves a lot of space because you don't have to have a two-terabyte test database as well.

If there were data integration services included with the platform then it would be interesting, and it would help us a lot.

We completed a short PoC using Nutanix Era last year to see if we want to do a pilot. We haven't actually implemented it yet, and we're in the process of organizing the pilot program. In total, we used it for about three months.

The stability of our PoC system was very good, but as we were only four people working on it and benchmarking it, there were not a lot of connection issues. I think the first thing we would want to do during the pilot is to simulate application connections and see how well it takes it. When you get that scenario of an application having database runaway connections, kind of simulate that and see how it handles it. But for the PoC, no stability issues whatsoever.

At the moment, we're waiting for approval so nobody is using the solution. However, if we go for the final implementation, the plan is to have two permanent Microsoft SQL DBAs, and then have an automation system that does most of the provisioning.

The DBAs will be there for monitoring and optimization purposes, but we intend to have the provisioning system fully automated so that users can request short-term or long-term data storage as they require. That will be provisioned automatically from our ticketing system.

I think the only limiting factor on scalability is licensing. Licensing costs will be the main scalability problem. If you have a large environment already licensed, scaling the resource allocation according to your performance needs is very easy.

We didn't make a lot of use of the technical support after the initial setup, so I can't offer too much about our experience. However, what I can say is the solutions architect was very good, very well informed, and able to return answers to our queries within a few minutes.

Prior to using Nutanix Era, we used VMware to create a service, and then we used to deploy by installing a SQL server.

Our PoC was deployed on the Nutanix hosting cluster.

If you have experience as a DBA, the setup is very straightforward. If you haven't had any database administration experience before, this is definitely going to be easier than doing it from scratch on your own, thanks to all of the guidelines that they add for you. My database set up in Era is mid-tier. It's not as complex as doing it from scratch on your own, and for a DBA, it makes it a lot easier.

Our initial setup for the different scenarios took us about two days, and that was rolling out 14 databases on nine servers. The implementation strategy for the PoC was basically to first set up all the server hosts that we would need with the different resources, and then deploy using the Era tools for each one of the different scenarios.

I think the only reason that we took two and a half days to do it was so that we could get used to how Era does it. In the final part of the PoC, we were able to remove and redeploy database engines in 15 minutes at the most, and that was for the availability group. There were a few niggles that you have to overcome with availability groups, which Nutanix makes easier, but doesn't completely take away.

We had our Microsoft team involved, which was four Microsoft DBAs. However, if Era is fully up and running for our environment, one person should be enough because most of the time, it's just going to be someone to approve. We're not going to need an entire team. This means it will be one person to maintain, without a lot of overhead.

Initially, we had help from one of the Era solution architects, just to help us get to know the Era system. After the third day, once we understood how the process flow works, we didn't need any third-party intervention at all.

We do expect a return on investment, mainly on the number of people we would need and the number of man-hours that we currently spend, on which we're going to save. Because we are an educational institution we're nonprofit. We are able to provide services but we don't actually ask our users for any money. This means that the return on investment calculations will probably include things like support for research outputs and support for dynamic user requests. But from a costing perspective, it is going to be a little bit difficult to do that.

Currently, we're supposed to have eight people with the number of databases we're running. I think that our team of four people will be able to handle this, plus their other duties. Ultimately, we will not need to utilize the remaining four FTE. It's pretty substantial when you add it up if you look at what a SQL DBA costs these days.

We have yet to implement our pilot program and we're waiting for Nutanix to come back with the pilot quotation for costing.

Licensing costs will be the main scalability problem. If we need to start adding resources in terms of hardware then it's easy but adding software licenses normally causes a problem for us, so it is not as straightforward.

I don't expect that there will be any costs in addition to this because most of our hosting for the Nutanix system is done on-site. Furthermore, we're not going to use a hybridized Nutanix Era implementation. Other than for per-CPU licenses, I don't see any additional costs.

We did not evaluate any competing products. We had done an evaluation of Nutanix for our hyper-converged infrastructure and this suggestion for Era came from them.

The one thing that drew us to Era is the constant improvement cycle that they have with the different database vendors, where they do implement best practices as the database vendors change requirements and change their architectures. Since we started with the POC, we started with Microsoft SQL 2016. We also moved over to Microsoft SQL 2019 during the POC and for both of those cases, they were able to actually help us with implementing best practices according to Microsoft for both of those engines, which do differ quite a lot. The 2016 version has certain prerequisites and storage requirements that 2019 changed to an extent.

For example, in 2016, Microsoft requires that you have a TempDB storage drive dedicated to the TempDB space. In 2019, they changed the requirement to say you should not have more than four TempDB files per drive to ensure that you have enough IOP. It is helpful that both of those scenarios were catered to by Era internally already.

During our PoC, we did the technical side of testing Nutanix, and we did some benchmarking on the performance, but we didn't really get into the performance optimization monitoring and tuning of the databases. Assessing and optimizing database performance is one of the reasons that we plan to do the pilot project.

The delay was that we couldn't put our actual production systems online during the PoC because it's a bit difficult to intermix PoC with production. The plan is that when we go into the pilot, we will select better production databases that fit the different use cases, and then we will do the performance tuning and see how those tools help us.

The one thing that I'm uncertain about that might be important would be the monitoring and performance tuning capabilities. Since we do have a lot of other tools and experience with that, we might find that Era doesn't quite cater the same way, or we might find it actually does better. I'm not sure at this point.

The biggest lesson that we've learned is that being able to automate almost 90% of the provisioning process is something that we never thought would be possible, mainly because there are so many different nuanced things that you have to do when you provision the database server. We tried to do manual scripting with PowerShell, which didn't always go as planned. But with the provisioning scripting that Era gives us, we finally have an option for a tool that will automate a lot of the stuff that we do, which means that in turn, we can focus on the important things.

The one piece of advice I would give for anybody who is considering this product is to look at your data storage profile, and see how many different database vendors and database engines you use. If it's anything more than one then definitely, go for Era. It makes life for managing these different types of database engines a lot simpler.

Because I haven't been using Era for at least a year, I don't really know if there are any issues that we haven't seen that might pop up. So far, everything looks good, but over time, little niggles may appear. Considering this, I cannot say that it's a perfect solution at this point.

I would rate this solution an eight out of ten.