MySQL Reviews

I'm using it to create a small database for a project that I'm working on.

The easy access to the data and the ability to sort the data with multiple methods are very valuable features.

It's quite easy to grasp and is really well documented, which are huge plus points.

Sometimes, I get lost in the toggles and buttons, and a better visual design would be nice. The layout is not user-friendly or efficient.

I would like to be able to sort the data easily without having to do a request to get the table out of the database into the web page. At present, I can't do it directly inside MySQL; I have to do a request and print out my request into a web page.

The stability is really good. I haven't had any issues with it.

The scalability is good.

The initial setup is easy.

I learned to use it in class, and the setup was quite fast because the teacher really helped us to gain access and take the first few steps. The setup took a few hours at most.

I installed it myself.

I use a free version at present.

Plan how the data will be constructed. I had to delete an entire database and start over because I didn't organize it properly. That was a huge block.

I would rate MySQL at eight on a scale from one to ten.

We're using MySQL for data warehousing and logging.

Even for the best database, we always want the database to perform much better, so we wish MySQL would be much better, in terms of performance. When they release a new version, they mostly concentrate on scalability and performance.

I've been using MySQL for seven years.

The stability of MySQL is good.

MySQL is a fully scalable product.

The initial setup of MySQL was easy and straightforward. You can complete the initial setup for this product within a few hours.

It was the technical team who did the setup for MySQL. We had two or three engineers who took care of the deployment and maintenance of this product.

MySQL is very cheap. In fact, it could be free. They also have a yearly licensing option. I don't remember paying for additional costs, aside from the standard licensing fee.

I evaluated Oracle Database.

I'm using the Enterprise version of MySQL.

MySQL is a good database. We are using it, and we'll continue to use it.

I've never contacted the technical support team for MySQL. I have no complaints.

I can recommend MySQL to others who plan to start implementing it.

We don't ask for new features on a database. When we take a database, we take it because of fixed features, e.g. its current features. It's not an application. It's a database. We are fine with whatever features MySQL offers now. We never really thought about whether we want more features on this product.

I'm rating MySQL an eight out of ten.

Our primary use case for MySQL is for running applications on our Linux boxes. We have very few applications that run online, but we use MySQL on those boxes, primarily for our email system. We haven't considered working on cloud, so all our solutions are on-premises. 

One of the most valuable features is MySQL's ability to run our email system. We use a system called Colab. 

MySQL could be improved by adding more automation. There are no additional features I would like to see that I can think of at the moment. 

I have been using MySQL for a few years. 

This product is stable. I'm very satisfied with the performance. 

Since MySQL is running our email system, there are around 200 users. It's installed on one of the servers and the admins are the ones who interact with the system itself if the need arises. 

I have never contacted Oracle's technical support. If we have any issues, we've got some recommended support people here in Zimbabwe that we contact. 

I didn't use any other solution before implementing MySQL. We also use MariaDB, but not on a very big scale.

The installation was a very straightforward process. It took about a day and we did it ourselves. 

We implemented through an in-house team. One person, the admin, can handle it. 

We are using the free version of MySQL. We prefer paying for a yearly license. 

I rate this solution an eight out of ten. I would recommend this solution to others and I'm very satisfied with its performance. 

Due to the open source licensing model, it has allowed small businesses like ours to adopt enterprise-grade database systems without incurring significant licensing costs.

• Open-source
• Multi-platform
• Lightweight
• Simple to set up, configure and tune
• Support for enterprise-grade features like clustering, master-slave replication, even Sharding (to some extent) which is an advanced feature

It would be helpful if there were a graphical user interface to administer, configure, and tune it.

If it had something similar to Microsoft’s DTS engine then it would be the best database system out there.

For the scale at which my systems are operating, the software is stable. We are at most dealing with less than 10 million rows of data across all tables, and concurrent connections under 200 at our peak loads.

No scalability issues at the scale at which my systems are operating. One thing I did encounter with an earlier version of MySQL 5 – the mysql process will not automatically use available CPU cores on the server, even if it was a dual or quad core CPU. I was troubleshooting a scalability issue when I saw this, it maxed out just a single core and left the other three (in my quad core CPU server) idle. There was a specific condition / trigger that will make the mysql process span the other available cores (I can’t recall now but a quick googling likely will uncover this).

We did not subscribe to professional support from MySQL AB or Oracle. However, the wealth of community support is outstanding. Most of the issues faced could be resolved by knowledge shared by the MySQL community.

I’ve used SQL Server and Oracle for database systems. SQL Server is an excellent solution, in particular the DTS (Data Transformation System) which is not available for MySQL. Switching to MySQL for two reasons: 1) licensing costs 2) the application supports MySQL primarily, and has poor support for SQL Server.

Very easy to set up, relatively easy to configure, tune, and use the conf file, as long as you are comfortable mucking around in Linux conf text files and working from the command line (I am).

You could use the installer which would be the easiest way, but setting up by hand is not too difficult either – instructions can be found online and following them step by step usually works fine.

MySQL Enterprise Support is not cheap, though might still be cheaper than Oracle or SQL Server. They may not have local support depending on where you’re based, but there are many smaller agencies out there that will readily provide support. You’ll need to spend some time looking around.

I’d been using other database systems like Microsoft’s SQL Server and Oracle Database before trying out MySQL. There are forks of MySQL maintained outside of Oracle, like MariaDB and Aurora (by Amazon Web Services). I have not really tried them but I don’t expect very big differences; in fact, for most use cases you may not observe any difference. There would be the few unique features in MariaDB and Aurora that are not present in the original MySQL feature set (I know there are but don’t remember the specifics).

As long as your application supports it well, and you are familiar with the scaling options and its limitations, you can’t go very wrong with MySQL, as it is a very mature product by now. If you are fairly competent with servers and databases you could start off without subscribing to Enterprise Support, and may be able to get by quite well. If things get more complicated, or scalability starts to become a problem, then you may consider paying for help.

I use the product as a backend to my application.

The product is flexible and easy to use.

The interface could be improved.

I have been using the solution for seven to ten years. I am using the latest version of the solution.

I rate the tool’s stability a nine out of ten. The stability is good.

I rate the tool’s scalability a seven out of ten. We have four direct users and more than 1000 indirect users. We use the tool twice a week.

I rate the ease of setup an eight out of ten. The deployment took a few minutes. We need two system administrators to maintain the tool.

The deployment was done in-house. We need one system administrator to deploy the tool.

I rate the pricing a seven or six out of ten on a scale of one to ten, where one is cheap and ten is expensive.

We used different solutions before, but I do not know why we switched to MySQL. I recommend the solution to others. Overall, I rate the product an eight out of ten.

We use it for my clients. Basically any website that uses WordPress uses MySQL, so we use that to manage and run our WordPress websites. Some we have on a cloud, some we have at hosted servers.

It is part of WordPress and some clients are using it for eCommerce, and others are just using it as part of the website to give information.

The feature that I have found most valuable is its ubiquity. MySQL is everywhere, so if I need to find a developer to do things to it that I don't know, it's very easy to find someone who has expertise in it.

In terms of what could be improved, there is not anything that I can think of offhand.

Everything related to automation or improvements are external tools that are brought into it, so it has nothing to do with the robustness of the system itself - it is the developers and implementations that touch it. Those can be improved, but MySQL itself is fine as is. 

I would just say that it could be a little bit simpler to use.

I've been using MySQL off and on for about seven years.

Different hosting systems have different iterations of it. Whenever possible, I try to use the latest version, but usually I'm using a model or two back. But I'm not using the original, not by any stretch.

Everything that works with MySQL is stable. If it's a bug, it's due to the developer who has miswritten a piece of code. The code itself is perfect. It's the application of people who attempt to make changes where the issues come in.

In terms of scalability, I have not done anything bigger than a couple hundred people a day on a site, so I really couldn't tell you about that.

Our clients are small businesses, almost all of them with less than 50 employees.

Previously, and I am talking almost 20 years ago, we would have used Microsoft Access, which is not a relational database and it's not iterative, so you can't have multiple people working on it, whereas MySQL is a system-based database, so multiple people can access it at the same time.

In terms of the initial setup, you definitely need to know what you're doing, but it's not illogical. The database rules and how they work are very clear and concise. To execute MySQL is fairly straightforward.

MySQL is open source so it's free.

My advice to anyone considering MySQL is to check the forums and do your homework.

On a scale of one to ten, I would give MySQL a 9. It would be a 10 if it was simpler to use, but as it is, it's about a 9.

We developed a network monitoring software and used MySQL as a backend database.

We utilized the two most common and popular MySQL database engines, MyISAM and InnoDB.

We store collected monitoring data and configuration data on MySQL. Also, our network monitoring solution reporting module is based on the MySQL MyISAM database engine.

We use both Windows and Linux versions of MySQL, and we utilize the backup and recovery features.

To summarize, our primary use case is the embedded DB component for our network management software.

MySQL is a popular database platform for businesses because it is extremely easy to use. It is commonly used in combination with PHP and Java. For instance, someone with little to no knowledge of MySQL can easily establish a database connection and start programming immediately.

So MySQL improved our developing process speed. MySQL is a very popular and well-known database solution, so it is easy to find a MySQL developer.

MySQL performance also improved our NMS solution performance.

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses.

MySQL advantages and valuable points include:

• MySQL is a very powerful program in its own right. It handles a large subset of the functionality of the most expensive and powerful database packages.
• MySQL uses a standard form of the well-known SQL data language.
• MySQL works on many operating systems and with many languages including PHP, PERL, C, C++, Java, etc.
• MySQL works very quickly and works well, even with large datasets.
• MySQL is very friendly to PHP and Java at the same time. Both PHP and Java are our development languages.

The two most common and popular MySQL database engines are MyISAM and InnoDB. Database engines provide the underlying functionality for MySQL to work with and process data. MyISAM is the default engine for MySQL for versions earlier than 5.5.5 and functions well in most scenarios.

However, depending on your needs, there are situations where another database engine, such as InnoDB, may be the better choice. For example, InnoDB supports transactions, whereas MyISAM does not. InnoDB also provides support for foreign keys, whereas MyISAM does not.

When it comes to supporting big data, there is space to improve upon the database engines that are supported by MySQL. An example of this is the Vertica DB engine (https://en.wikipedia.org/wiki/...), and offering support for it would be valuable.

We have been using MySQL for more than ten years.

Previously, we used MSSQL and switched to MySQL because of performance issues.

After installation, the maintanence is easy for an end-user.

MySQL is released under an open-source license, so you have nothing to pay to use it.

Our main use case for MySQL is for applications and seamless migration to the DR site. And the application in this case is an airport application.

I can meet the RPO in almost real-time. This changes the customer experience. That testing still needs to happen, but that is one of the advantages of MySQL. We have found MySQL to be a very sturdy and strong database. And I have run it in a solution where it's almost real-time, so it runs very efficiently.

MySQL's clustering features are very strong, and you can automate scripting, so that helps. We wrote a Terraform script and ran it. 

Rather than going in-depth about the technical features, which a technical person can directly tell, I would say that MySQL should be able to adapt to the next framework. The 5G framework means an unstructured framework. So if MySQL becomes smoother and more adaptable, it'll be easier. In terms of new features, automation is always the biggest demand from our customers.

I've been doing pre-sales and working with MySQL since 2007.

I would say that MySQL is definitely stable, but its scalability has yet to be tested. I cannot say right now.

We follow an agile strategy, so deployment is done in parallel. In comparison to other databases, I have always found MySQL to be the most efficiently managed. Of course, I don't discount Postgres, but MySQL deployment always has gone smoothly. I've never had an issue during migration, even on the granular level. UID numbers, which we commonly face in Microsoft SQL, have never been a problem with MySQL.

We use the implementation partners for OEM. 

We get the standard packages, but mostly MySQL is freeware. You pay for a license to get the upgrades. We pay for an enterprise license if that is required, but that's not in every case. It depends.

I would rate MySQL nine out of 10.