MySQL Reviews

We use MySQL as a light database engine to provide database service to our web application. 

Almost all of our software engineers use MySQL.

We want to continue using MySQL but it merged with Oracle and the scalage changed. After they merged, we tried MariaDB. 

For two years, we tried MongoDB and prepared for application migration; all because the scalability changed when MySQL merged with Oracle. 

This solution is very easy to use. It's stable and very quick. MySQL is a light database. It's not very complex. It's easy to develop, easy to maintain, and easy to back up and restore. 

Our software team has been using MySQL for more than eight years.

It's hard to say if MySQL is scalable as we've never tried to scale it. 

We have never had to contact support. 

We installed MySQL Database on our server. It took roughly 12 to 13 minutes to install it. 

Installation was done by our software team's engineers — seven to eight of them.

We've never bought a commercial license. We just use the open-source community edition. 

We evaluated other databases and products, including EnterpriseDB and PostgreSQL. The latter was scalable, but it wasn't easy to use. MySQL is much easier to use and install. Before MySQL merged with Oracle, our software engineers were very satisfied.

We recommend MySQL to our customers and other partners. The only problem relates to the business strategy from Oracle. For this reason, most MySQL users are considering migrating to MariaDB.

Overall, on a scale from one to ten, I would give this solution a rating of nine. We're very satisfied with MySQL. If we could scale-out further, I would give it a ten. We need a database cluster or a scalable database solution for our future applications.

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 currently using MySQL for the contact center database, and it is in the cloud. I have also used it in other projects for database and CRM, and it was on-premises. I have used it in 20 projects.

It is easy to use. It is simple to implement, which makes it suitable for our projects because we have deadlines. MySQL is also open-source, which is another plus point.

Its performance should be better. When we use big data, it is slow in performance. We should be able to use mirroring for improved performance.

I have been using MySQL for nine years.

It is very flexible. It could be because I'm familiar with MySQL.

I have never contacted the technical support of MySQL. If I have a problem, I find the solution from Stack Overflow.

Its initial setup is easy. I only need a maximum of one hour for the installation of MySQL.

It is open-source.

I would rate MySQL a nine out of ten.

We use it for financial transactions such as money remittance.

It has a community version. When I have to create a new database, I have no problems with licenses.

It can have better monitoring. In addition, the enterprise manager should be able to cater to more than one virtual machine. Currently, you need one license per server. It seems a bit too much to get one license for one enterprise manager. I hope the enterprise manager for MySQL can accommodate more virtual machines for MySQL.

I have been using this solution for a decade.

It is stable.

We have categorized the amount of data we have as big data, although we haven't really been using it much.

We have 2,000 people in our company, and we have over 100 virtual machines installed with MySQL.

Because we are using the community version, we haven't had the chance to contact the technical support of MySQL.

It is easy for us. After a few trials or installing it a few times, we have benchmarked and created best practices for installing it.

It has a community version.

If you are not into command-line usage, I don't think MySQL is for you. I found MySQL easier to use by using the command line rather than by using the workbench. The workbench is comparatively slow, especially when exporting.

I would rate MySQL a seven out of ten.

We use MySQL to organize data, analyze information, and make decisions for the company. We also use it to process information from different areas in the company.

What I really like about MySQL is the opportunity to search for information and organize it any way I like. If you know the queries and you add the code, you can organize information any way you like.

MySQL needs to be more accessible and user-friendly. The person working with it needs to be trained in MySQL to have the necessary skills to control the database and analyze data. It should provide better customer experiences.

I have been using MySQL for one year.

The initial setup depends on your knowledge. If you know the principles, except when it comes to queries, it's easy. But if you don't know anything about MySQL or SQL, you can't do it. It took us about six months to set up and deploy MySQL.

I would tell potential users that people in production have to be trained to use MySQL. They should take some courses, and get certificated. This will show them how to use the principal tools and provide some context about how MySQL works. 

On a scale from one to ten, I would give MySQL an eight.

We are an asset management product company. Our product is deployed on the cloud and the backend database for it is MySQL.

The technical support should be more knowledgeable and available worldwide.

We have been using MySQL for the past five to six years.

So far, it has been pretty stable and I haven't had any problems. We plan to continue using it in the future.

MySQL is very scalable, so I don't expect any challenges.

We have a contract with a third-party for support. So far, it has been working fine for us and I don't see any challenges. That said, having worldwide support is something that would be an improvement.

Prior to MySQL, we did not use another database for this purpose. We built our core product directly on top of MySQL.

The initial setup seemed pretty decent, so I don't see any challenge in that regard.

Our in-house DBA team installed it. We have one DBA and one junior.

This is a good product and I recommend it to others.

We use it as a data store and from that perspective, we get everything we need. We don't have any complaints about features such as analytics, reports, or dashboards.

I would rate this solution a six out of ten.

We only support the backend and only carry it as a database. You can do what you want on the database to create the schema and to manage the rest of the organization.

Errors that come from MySQL need to be more clear. In Oracle, for example, you have the aura and you have numbers, you can easily find the error. MySQL should follow the same as in Oracle.

Stability needs improvement and the backup needs to be enhanced.

We have been using MySQL for years.

We are using the latest version. Normally we do upgrades and we follow the upgrade path.

It could be more stable.

We have 15 customers, but I am not sure of the number of users we have.

I have not dealt with technical support.

It was easy to install. It only took ten minutes.

We have a huge database team as we are supporting many regions.

We implemented this solution ourselves.

We plan to continue using this product. It's good, and I can recommend it to others.

I would rate this solution a seven out of ten.

We are interfacing it with MicroStrategy. There are ODBC connections. We have 10 to 12 users in our company.

We are assessing the possibilities of moving to the cloud. We are not yet sure if we are going to move to the cloud.

The replication feature is the most valuable. We are replicating our servers.

It should have some code analytical functions. It can also have a monitoring tool.

I have been using MySQL for ten years.

It is stable. We are not dealing with a huge database. Our database is not more than 1 TB, so we didn't find any problem.

I haven't seen a need for scalability.

Their technical support is good.

The initial setup is easy. We are using it on Linux, and our server is on CentOS.

I would recommend this solution. I would rate MySQL a nine out of ten. I find it almost perfect.