MySQL Reviews

Small to medium-sized business usage. The main advantage is the very large user base. This enables users to fix about any issue by answering any question. From a technical viewpoint, MySQL is on par with the other open source database solutions.

Due to the large user base, a large amount of software modules and plugins for rapid application development are possible. From an operational viewpoint, this is also a very big advantage.

The large user base and the amount of available plugins and modules. A lot of the software components have been trialed and tested for often more than 10 years. It is rock solid from that viewpoint.

It does not stand out regarding scalability. When the company size increases, the user base having actual experience with (very) large MySQL solutions is reduced.

No, it is rock solid.

Yes, other solutions have better features and better performance.

Not applicable.

No.

The initial setup is very easy with very good online support.

Implementation was done in-house.

Not applicable.

When you know the setup will continue to grow, make sure you have the paid support. 

MariaDB/Galera.

We use MySQL for internet applications. 

MySQL is easy to integrate. It works with just about every language. 

Security is a concern. MySQL could have better security features. 

I've been using MySQL for several years. 

I've never contacted technical support. It is done on the internet. You have all the support there.

Setting up MySQL is no problem at all. I can do it by myself, and it's deployed almost instantly.

I would rate MySQL nine out of 10. 

It is deployed on local servers, and we are using version 8. The whole company uses our database. Our users don't communicate with the database directly. They use a web interface. All programs are deployed using MySQL. We have hundreds of thousands of users accessing MySQL via the website. Two of us manage the database, but it's enough for only one person to manage daily operations. 

As we are using the latest version of the database, it has many functions that have improved it. There are many new features in this version, and it is more powerful in what it can achieve.

MySQL has a lot of documentation, and bug fixing is better in the latest version.

We have been using MySQL for about 20 years.

It is very stable.

MySQL is scalable. We didn't scale it via the database tools provided but on the program side. However, it is easy to scale it using the functions provided with the product.

The support is fast and helps to find faster fixes to existing bugs. They recently advised us to downgrade to fix one particular bug, which resolved the problem we were having.We only use technical support for bug fixes, and the calls are usually closed quickly.

I was able to install it myself in about half an hour.

MySQL is free.

We have also used PhpStorm and DataGrip.

I would recommend that others use MySQL. I would rate it 10 out of 10.

We are using it for RADIUS protocol, which is for network access. We are tracking the duration of user stations.

Table partitioning is most valuable. It is easy to use.

I am looking for the Temporal SQL feature, which basically means that there is complete history for each table. This feature is currently available in MariaDB.

PostgreSQL has something called a foreign-data wrapper, which is another way to access external data from inside. MySQL could have a similar feature.

I have been using this solution intermittently for six months. 

It is stable.

It is scalable. We currently have six users.

I don't have any experience with their technical support.

Its initial setup was straightforward. It took 10 minutes.

I did it myself. We have two people for its deployment and maintenance.

I am not paying, but I am not sure about the exact licensing requirements.

It is always compared with PostgreSQL and Microsoft SQL Server.

I would recommend this solution to others. I plan to keep using it.

I would rate MySQL an eight out of ten.

I'm not involved from the database side as much. I primarily use it for reviewing the data structure as the architecture before I build a data model in our BI tools.

General querying is pretty much what I do, and also analyzing data types and data structures within the database itself. I review the data structure within them. And I use that to build the data model, which we have in our reporting environment. That's primarily all I use it for.

What it would compare it to, from my point of view would be, Microsoft SQL Studio. I find the Microsoft solution a bit better. But mostly in terms of the UI layout, I would say. I just find it a little bit more efficient. But to be honest, I can work equally as well with both.

I've been working with MySQL for two and a half years. 

We haven't experienced any issues with scalability.

I haven't directly contacted their technical support. 

I haven't gotten feedback from the IT team.

The initial setup was pretty straightforward. I would have worked with our IT team in terms of the initial setup. In terms of connecting to the database and to the data sources, it is pretty straightforward.

I would rate MySQL a seven out of ten. 

To make it a perfect ten, they should improve the UI. It's got quite a narrow range, and there's a lot more obvious to the database side than what I deal with. The UI is not quite as sharp I would say as the Microsoft solution. In some cases, I find that there are better shortcuts available in Microsoft solutions.

If I was choosing, I would probably lean towards Microsoft. That may be just a purely personal preference. My use of MySQL has primarily been from a data integration point of view, a data architecture point of view, and reviewing the database itself, and the data structure, data types. In my role, I don't define data and I don't build the database, I'm purely on the interrogation and the analytics side. I probably would find the Microsoft solution slightly better. But MySQL does absolutely provide what I require from that point of view. So I would recommend it, yes.

We are an IT services provider, so the solution is for our customers. I can't answer for the customers in terms of how they use it. 

Typically, customers are running applications that need to connect MySQL and to store some of the data.

The solution is free to use, which is its most valuable aspect.

The interface is quite good.

The stability and scalability are very good.

Overall, it's an excellent solution. We don't have to implement anything else.

We haven't noticed and features that are lacking.

From a user perspective, the initial setup could be simplified a bit.

I've been using the solution since 2000. It's been about 20 years now since I first was introduced to MySQL.

The stability is good. Neither we or our clients have had to deal with bugs, glitches or crashes. Everyone's been satisfied with it. Stability is one of its best features.

The scalability of the solution is good. We haven't had trouble scaling at all.

We're using the community version of the solution. I don't have any complaint with the level of support, however, it is online and there isn't a support line.

The initial setup isn't always straightforward. Sometimes it is complex. For example, if you are doing a database expansion. For database expansion, you have to configure it and you have to know SQL quite well. You have to juggle a few things, which makes it complicated. However, from an IT perspective, it's a good tool, so it's worth the effort.

The solution doesn't cost anything to use. It's absolutely free.

We are IT services provider, and provide this solution to our customers. It's typically installed on a dedicated server.

When we are working with it, we are doing SQL queries, and on top of that, we are using MySQL to do some reporting as well. It does what we want it to do and our clients are also happy with the results they get. It's a fine solution.

I'd advise those considering working with the solution to be patient.

We don't have any partnership MySQL. We are mostly a Microsoft partner. We mainly use the solution because of the community and the SQL server that's different from Oracle's server. From time to time we have to use MySQL.

I'd rate the solution eight out of ten. From our perspective, it's free to use, it's stable and it's fast and scalable. It makes it a good option for many organizations.

MySQL is strongly recommended for web applications and LAMP architecture systems. The most valuable feature of this product for me is its graphical interface which allows me to do the database administration easily. Another important feature is its reliability, the decent performance, and the fact it is an open source product.

It gives us the opportunity to create backups of our databases easily and loop through them with minimum effort.

I think that the stored procedures and the development tools to write and debug large queries could be improved.

I have used MySQL for about 10 years.

There were no issues with stability.

There was no issue with scalability.

We have not used technical support. The community is large enough to find the solution when something comes up.

We used many SQL database solutions like PostgreSQL and SQLite and NoSQL databases like MongoDB. The choice depends on the project.

The initial setup was straightforward.

I think that the Open Source product would cover the needs of most projects. In some cases, the advanced features are needed. They could use the enterprise edition, which is reasonably priced.

We have evaluated and used different products like SQLite. It depends on the requirements and the needs of the project.

I believe that it is the ideal solution for a variety of projects with a small learning curve compared to other solutions. It allows you to be efficient quickly.

Speed and stability of the MySQL DB are the most valuable features since we use it as the data store for most of our web applications.

Before we used MySQL, we used to access the data used for the dynamic web pages directly from our enterprise data stores and that was a massive performance bottleneck. With MySQL, the data can be accessed much faster. This allowed us to create more complicated web systems, such as the corporate message system and a credit card paying system.

From where we are, most of the improvements are being handled. With the new improvements that were introduced in MySQL 5.7 and with the testing that we have done to this point, we are looking at updating our web development environment to make better use of the new features.

With the push from MySQL to implement database engines which can provide the same functionality as PostgreSQL and MongoDB, we are looking at application development that leverages this functionality on our current MySQL production database. Seeing that MySQL can provide noSQL document storage the same way MongoDB can and still have a SQL data source next to it creates the possibility of using the best features of both to achieve the desired application result without changing our current infrastructure drastically.

It must be noted that we are still in the process of experimentation to find the best ways of utilizing these data technologies in our current enterprise applications, but not having to move to other database providers to have the functionality means we can experiment without the need to change our base processes. So when I say that the improvements are being handled the MySQL development team have given us access to functionality which we started to look at about two years ago.

I have used this solution for around seven years with upgrades.

There were no stability issues.

We did experience a few scalability issues, but we decided to rather go for a bigger server than creating a cluster and that worked out very well.

The technical support is very good

The setup was very straightforward since the out-of-the-box MySQL's performance is already very good.

We had to do some tweaking over time, but nothing too major.

The enterprise version has a number of extra components that makes it worth the price, but if all you want is a stable DB for web applications, then stick to the open version.

We use enterprise because we use the PAM connector and the DB firewall, if you are looking at the pricing for implementing a separate data firewall, it is more than what you will pay for this solution.

There were not a lot of other options open to us.

Ensure you know what you want to use it for and make sure it is the right fit for the job.

Do not allow developers to tell you what your DB should look like, as that is the best way to performance problems. Use the MySQL Workbench and MySQL Monitor.