MySQL Reviews

MySQL gives us all of the critical features that we need in a database, but without the costs.

The most valuable feature is that we can implement clustered solutions.

I would like to have features that allow us to jump between the cloud and our on-premises system.

I have been using MySQL for about 20 years.

MySQL is a very stable product.

I know that it is scalable, and in fact, that is why we chose it. We always have it in mind that in some number of years, you have to scale the solution to something different in terms of architecture.

As it is now, our databases are not big. They are critical, but not large in size. We are not dealing with Big Data.

We have never contacted Oracle for MySQL support.

The documentation that is available is enough for my needs.

This was the first database solution that we used. I have used other database products such as Oracle, for example. Oracle comes at a heavy cost.

This is an open-source product that can be used free of charge.

This is the product that was proposed to us and we implemented it.

MySQL is a product that I can strongly recommend. However, it is important for you to have the in-house knowledge to support it. Some level of in-house expertise is necessary, otherwise, you will have to rely only on external opinions. In my opinion, that's not good. Sometimes they have good intentions but don't understand the reality.

I cannot give MySQL a perfect rating because we don't use all of the features. That said, I can tell you that I am totally satisfied with it. It's a very stable product and it's something that is not difficult to deal with.

I would rate this solution an eight out of ten.

We primarily use the product for small applications.

The solution is great for small applications in particular.

The performance is good.

The solution originally was designed as an open-source product. It has a community edition that anyone can use for free.

The initial setup is simple and straightforward. 

I have doubts about its overall stability. It's something that they should look at.

As an open-source product, there isn't really any technical support available if you get into trouble or have issues.

There isn't much scalability potential in the product.

I've been using the solution for a very long time. It's been years at this point.

The stability could be better. It's not as stable as I would prefer it to be. 

It was originally designed as freeware, as an open-source project, and the community wrote the solution. However, they've made it worse over time.

That said, the performance is pretty good.

The solution is not that scalable. It's not something you should pick if you need something to expand significantly.

While I can't speak to how many people use the solution in our company, I can say that it is used by several departments and divisions.

The solution is open-source and managed by a community. Therefore, there is no technical support available to users. 

The initial setup is very easy and quite straightforward. It's not overly difficult or complex. 

That said, I was not a part of the original setup and therefore cannot speak to how long the deployment took my team.

We didn't need any assistance from integrators or consultants. The setup was handled in-house.

The solution is open-source and free to use. We have the community edition. We don't have to pay to use it right now.

Right now, Oracle has taken over the business of MySQL. Now, it's standard that you have to pay money for the license. That's why we are shifting all our databases, the small, small databases, from MySQL to Oracle. We do have extra data, so we do require a license.

Currently, we are using the previous version of the solution. I can't speak to the exact version number, however.

I'd rate the solution at a five out of ten.

I wouldn't recommend it to other organizations at this time.

We use this solution for the database.

The connectivity with PHP is quite good.

It is easy to integrate, and the fees are less than Oracle and other services.

MySQL is good but it should be able to handle the large transaction levels that Oracle can. It should be able to manage large amounts of data. We have experienced some issues when we are handling a large amount of data in MySQL.

The memory consumption it's using is very high at times, and the default parameter settings are not quite good automatically. We need to tweak the configuration as per the requirements. This is an area that can be improved by giving some guidelines and direction. 

On the database side, it should be really lightweight, and the data structure should be like MongoDB.

It should put less load on to the memory and it should be able to handle maximum data.

I have been working with MySQL for approximately five years.

The solution is stable but there is an issue with memory consumption at times.

I have not contacted technical support. I am using MySQL with Zabbix and when I have an issue, I contact Zabbix who resolves the issues on their end.

I am a developer and I handle the other side of things. I rely on the DB team to handle the maintenance and deployment. My knowledge is very basic.

It's cheaper than other solutions.

For one level of data, you can use MySQL. However, for large amounts of data, you will have to find other databases.

Overall, it's a good solution.

I would rate MySQL a six out of ten.

It dramatically improved use for several of my customers.

This depends on my customers' use.

SQL and NoSQL use.

When configured correctly, no stability issues.

When configured correctly, no scalability issues.

Very good.

MySQL Support Services by Percona. I switched to Oracle MySQL services because of a better ROI.

There is no obvious answer. It depends.

Depends on the customer's needs. 

MariaDB, MySQL Support Services by Percona.

Stick with the source, stick with Oracle MySQL as the leading vendor for MySQL technology.

• SQL Merge
• Replication
• Views
• Stored Procedures
• Triggers
• Cursors

This is just like the enterprise grade Oracle DB. MySQL now supports replication (master-master or master-slave) of our DB to support our company's multiple geo-locations and PoPs.

It supports the original Oracle SQL operations such as Merge, as well as the creation of Views to your tables. This brings additional convenience to our organization.

The main benefit for us is that it's totally free, unless you need to pay for support.

I would like to see additional side management tools and IDEs.

I used this current version for one year. I used previous versions for over ten years.

There were no stability issues.

There were no scalability issues.

We didn't need any technical support. I would guess that Oracle support is top-level.

We did not use a solution prior to this one.

The initial setup was straightforward, user-friendly, and easy. In most cases, if you use the Linux-based versions, it comes as a standard Linux package. You can get it installed by using AptGet, Aptitude, or Yum.

Just pay for any license if you need some enterprise support for your project or any additional support tools that Oracle ships with the enterprise version. During the development stage of your project, you can just use the free community edition.

We evaluated MSSQL, Oracle DB, Informix, and MariaDB.

Go with the Linux version. It is more stable and manages the system resources better.

• Speed
• Cost

MySQL provides a low cost and effective SQL Database solution for smaller companies that don’t require the overhead and cost associated with RDBMS tools like Oracle

Replication and HA features, but that is to be expected at this entry point

10 years.

No, the deployment of MySQL is very easy as it is usually a part of Linux distributions and most hosting services provide a MySQL database as a part of their hosting service.

No, MySQL has always been a stable database. If there are sufficient resources on the server to run the database it will do fine.

None that I have run into. For really big databases I have always used Oracle.

There is plenty of support available on the internet. I have never really needed to use or activate a support contract for MySQL

There is plenty of support available on the internet. I have never really needed to use or activate a support contract for MySQL.

Before using MySQL I used Oracle and Informix for RDBMS.

The initial setup was easy as there is usually a version distributed as a part of the Linux distribution.

I have always implemented MySQL through and in house team.

The initial setup cost and maintenance costs are built into the OS costs for all of my implementations and are insignificant.

I usually look at MySQL, PostgreSQL and Oracle.

MySQL is a great RDBMS, but make sure it will integrate with all of the clients you will be using and the rest of your infrastructure. The problems usually have more to do with other products supporting MySQL than MySQL itself.

I use MySQL as middleware to get the extracted data from the database. I work with MySQL as an administrator to set up the whole platform. And I document the recipe for setting up the MySQL database.

We are working with the latest version.

SQL is just a relational database. It is open source. It's pretty good. I have been using it for a long time.

Because I am the middleware guy I'm not the SQL database administrator. If I have any issue with it, I'm going to contact the right person. Sometimes, not because the version is not the latest version, there are some issues with it. Sometimes there's an issue with the server which creates issues with it. Then, when the administrator checks the status and makes notes, it works normally and the problem is fixed. With a big company you are not going to work directly with the MySQL database. We are the end user and not the administrator of the SQL database.

For MySQL, in terms of the usage or as the end user, I don't have much to recommend, as long as the query latency meets your requirements, it will be great. Otherwise, it's the horizontal scalability and you get more parallel in the implementation in terms of the SQL database regardless of the usage. This is probably much better than the vertical in terms of scalability.

I have been using MySQL this year.

If you are working in the cloud platform then you do have scalability because the cloud platform is usually AWS or GCP, and they provide this kind of scalability. If you get some issues with the query and latency or something like this, that is an issue of scalability and you can just adjust the horizontal or vertical scalability to meet your requirements.

But the company I was working with was a very big company. It's more than several thousand people and they usually have a lot of data that they are going to store in the MySQL database. They gather the data from the SQL database and then transfer it like ETL and you get data from all the different distributed systems and then put them into the centralized MySQL database. After that you're going to visualize this kind of data so that you can use the Power BI or that kind of tool to generate reports or to create a dashboard for the system. This company had its platform on-premises, but right now they are moving these technologies to cloud. That's why I'm talking about the scalability in two different ways cloud and on-prem.

For technical support, I'm the end user so I extract data or visualize the data from the SQL database. I didn't get too into the daily maintenance of the database.

The initial setup for the SQL database is not complex and it even integrates into the platform. You set up the recipe and then just follow the build book. Then it works as long as you follow the procedures.

Regarding the price, because it's the open source they have different licenses. Even for open source there's a license for the enterprise. I don't think it is expensive. Also for the scalability in the cloud, the price is based on the usage, such as, how much data you transfer.

For the best usage right now, the trend is to move the platform from on-premise to cloud. Then, you you really have the best flexibility to scale down or scale up based on your usage. You can make full use of the resources and then pay for whatever you use. Because if you have it on-premise you always pay the same price no matter how much usage you have. So one of my suggestions is if you plan to set up the platform for MySQL, it would be best to go directly to the cloud solution.

On a scale of one to ten, in terms of the usage for the middleware team and the end user of the SQL database, I would say it's around an eight at least. I cannot say from a  database administration perspective.

To determine what would allow me to give it a 10, I would first have to get more experience using it on the cloud version.

We are doing POCs for our clients in our testing lab, and if a POC is working fine, then we give it for the production release. 

It has a lot of features. The RDBMS, consistency, and multi-user features are valuable.

We want high availability and replication features, which are currently missing in this solution. It would be great if they can provide an in-built replication feature, similar to Oracle RAC, in MySQL.

I have been using this solution for the last two years.

It is a stable RDBMS. There is no doubt about that.

We have been using it for POCs. It has been consistent for a hundred users. Currently, we have three groups that use this, and each group has 20 users.

I have not contacted their technical support.

It is open source. We prefer it for POCs because it saves the license cost.

I would rate MySQL an eight out of ten.