MySQL Reviews

I used it for a small customer database company in England with 20 employees. They didn't have that much data, and we needed something easy to install and easy to run. This was my use case for it.

My main reason for using MySQL for this small customer database company and for some kinds of scientific projects was that I had to do the installation myself. I didn't have a database administration team behind me. Therefore, I was looking for something very easy to handle. MySQL is easy to install, connect, and do all such things.

Its scalability can be better. It is probably not as scalable as Oracle. 

I had some issues with connectors. I used it from a C++ program, and it required some work to make it run, but finally, it worked.

I have been using this solution for two or three years.

I used it for a small customer database company in England with 20 employees. There were only two people using it. It was really a small solution. For this purpose, it was perfect, but I'm not sure how it scales. It was just not an issue in this case because we had very little data. 

Their technical support is fine.

It is easy to install. It takes just a few hours.

I will probably keep on using this solution. If you have a limited amount of data you want to store in the database, and you don't want to spend a lot of time on administration, it is certainly fine. 

I would rate MySQL a ten out of ten. It was perfect for our use case. 

I use the solution for personal use cases like software development, mostly database bug systems.

I used the tool to build our website. It is used as a database to store information.

SKIP LOCKED is a valuable feature. It prevents us from deleting things we put in the database. It's mostly for background jobs in the software development site in MySQL 8. It is a new feature. The solution easily integrates with other tools and systems in our IT environment.

The full-text search feature must be improved.

I have been using the solution for the past three weeks.

I rate the tool’s stability an eight out of ten. We can create a database user schema. It's quite easy to update and remove in case anything happens. Backing up is quite easy. We have security features for the backup.

I’m the only user in my organization.

The product provides good documentation online.

It is easy to deploy the product. I deployed it on my own. The deployment took an hour. We deploy the product using Kamal. It uses Docker. The tool is deployed on the cloud. To deploy the solution, we just have to enter the password in the server and deploy it. It wasn't much of a hassle.

The tool is easy to manage and saves us time. It has much less complications.

We're using the community version. The tool is open source.

I also use PostgreSQL.

The tool helps us get the job done. It is not very complex. Overall, I rate the product a nine out of ten.

I've used MySQL in the past for a variety of tasks. 

I once used MySQL when I created a PostgreSQL database for club management tasks. This included handling registrations, events, and mailing notifications for payments and event details. It served as a source service provider.

The response time for support could be faster. 

MySQL's performance requires attention. For optimal performance, one should review and sometimes revise the code, particularly when using server-side scripting. To optimize performance, it's crucial to pay attention to your code. Sometimes, you may need to review your code to ensure it's efficient and doesn't unnecessarily access the database multiple times.

The performance issues I encountered were not due to MySQL itself but were related to my coding approach.

I have been using MySQL for ten years. 

I would rate the stability a ten out of ten. 

For my use case, it is okay. Basically, it's just me for development. Previously, all clients or members of the club accessed it. When there was an event, maybe 30 to 40 people would try to access the system simultaneously.

I'm using SiteGround for hosting the website and its servers. I've chosen a package with more than enough CPU and memory to avoid trouble.

I've used technical support for several times. Most of the time, it was quite okay with quick responses. Once, I had performance issues. It took some time to convince them, but they guided me on improving performance by changing some database functions in MySQL. It was a longer process, but it was eventually resolved.

Positive

The initial setup was easy. I work in an agile way, which means coding and deploying quickly. We had a few internal users but many external users accessing the website, though not the back office.

The back office was developed over years. It's not just about having an idea and executing it; it's more about testing and adapting the process, unlike the waterfall method, where you end up with something that may not be immediately usable.

As the main user, our deployment process wasn't as strict as in a big company. I conducted tests, had a testing process with use cases to review, and then deployed. It was less rigid than in larger companies, where there are separate testing and development environments.

I  have seen value and impact from using MySQL

I don't pay for a license. 

With my previous employer, we used Oracle.

Don't just use MySQL on its own. Always use it with other software around it. MySQL is very stable, but pay attention to the software you use with it, whether you develop everything from scratch or use open-source systems like CMS.

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

My primary use case for MySQL is with my products or websites for clients, and it helps me maintain relations with the best.

The relations in the database, the dynamic workflow, and the ability to connect with all columns. It's useful for e-commerce.

There is room for improvement in terms of the stability of the solution. 

I have been using MySQL for three years. 

I would rate the stability a seven out of ten. It does break down a little at times. 

I would rate the scalability a seven out of ten. 

The initial setup depends. For example, when working with e-commerce sites, it can be difficult to connect, and there may be failures. However, for other sites, it's easy.

Our organization is using MySQL by having it hosted through a hosting provider.

It is free. It is an open-source platform. 

Overall, I would rate MySQL a six out of ten. I recommend MySQL for small organizations and companies. For bigger organizations, one may need to consider other options.

You can also consider your project, budget, and organization while opting for MySQL. If it's a government or private project and what the product is. 

We use the product for database management, as a database engine.

We use it for different projects, mainly when we have lots of data and the customer can't afford to pay the license of SQL Server, which is not a cheap one.

That's the main reason you use MySQL or Postgres or other databases. It's less expensive. 

The solution is stable.

The scalability is very good.

It's a mature solution that's been around for decades.

It is very easy to set up the product.

The support in MySQL is horrible.

It isn't as reliable as an SQL Server.

I don't see MySQL being improved at all, like in the last 10 years. It has been at the same level for a long time.

Its stability is quite good. There are no bugs or glitches. it doesn't crash or freeze. 

The solution is scalable, however, sometimes you might have issues. You need to have the knowledge to make sure that you can scale. That said, there are a lot of used MySQL implementations all around the world, which shows that it's a proven product. It has been there for more than 20 years or so.

The support is not ideal. It could be better. It runs under Oracle, and Oracle support is not the best company when it comes to supporting - especially since MySQL used to be a free, open-source solution, and remains free. Oracle doesn't have this approach in its DNA. It's an enterprise and they're not into open-source ways of working. That's why sometimes we move from MySQL to Postgres, which is similar yet has the support in the community.

I've also used Postgre and SQL Server.

This product is not as solid as SQL Server. It's not like it's a lesser quality thing, however, it's not as reliable as SQL Server. The engine is a whole different engine. SQL Server is a full-featured database engine, and MySQL is based on what we call a file-based database. It's like flat files as a database engine, so it's an underdog, if you can call it that, when it comes to database engines. That said, it works fine.

The initial setup is not that complex. It's simple and straightforward for the most part.

The solution is open-source. We don't pay for it.

There are options to get professional support from Oracle and, for that, the pricing really comes up, therefore, it's not competitive anymore. For that reason, it might be even wiser to get Oracle Database than get MySQL and pay for the premium support.

We are just end-users. However, we are happy to work with them.

With Microsoft, we are a customer, partner, and vendor. We aren't partners with Oracle. 

I would rate the solution at a six out of ten.

They just need to assign a great team to MySQL, basically, and Oracle should just leave them alone to improve the product as the product hasn't been improved in the last 10 years. Since Oracle acquired it, it has been in decline. They need to do a lot, not in terms of features. In terms of the mindset.

I would recommend Postgres which is similar to MySQL, over this product. Even the clients are coming to us with such requests. They will flat-out tell us: "we hear that MySQL is having issues and we don't want to deal with Oracle and all that kind of stuff, so let's use Postgres." It's easy to migrate over. It's almost seamless, which makes it a very attractive option.

We use MySQL to manage business intelligence reports by linking them with Oracle database and Power BI. 

I like MySQL's feature that helps to automate things. 

The solution is expensive. 

I have been using the product for five years. 

I would rate MySQL's stability a ten out of ten. 

My company has two users for the solution. 

We have not contacted support until now. We have an onboarding manual. 

The tool's installation is not complex but you need to have experience to set it up. You need to download the solution and pay for it. The installation can be done within an hour. 

You need to pay upgrade costs every year. 

I would rate MySQL a nine out of ten. 

The primary use case for MySQL is to develop web applications, proof of concept projects with data collection, data manipulation, and data reporting on both Windows and Linux platforms. 

We also use MySQL to store the data that we receive from different projects and build data models. We can also develop reports out of it.

MySQL is used for small application use only and not used for enterprise-level business applications.

MSQL is free open-source software. This is the most valuable aspect for any company as it helps to reduce the cost.

MySQL is easy to use and, with basic knowledge of SQL, users can easily build SQL Statements. It helps to reduce project cost for development projects. It also supports a large number of embedded applications.

The backup and recovery features are easy to use without any complexity. Users who don’t have much knowledge of databases can easily use these features.

MySQL offers password encryption and offers a good data security layer to protect data.

MySQL platform independence helps the development and user community.

MySQL is a relational database and it is easy to install, handle day-to-day activities, and manage backups. It is compatible with a lot of other shared database solutions.

MySQL Workbench is the graphical user interface tool and it helps with development, data modeling, data migration, and day-to-day administration.

MySQL has cross-platform support for multiple operating systems. The backups on a Linux machine can be restored on a Windows machine, and vice versa.

MySQL supports multiple window displays and it is useful for developers and users who don’t have much database knowledge.

Improvements are required in character set support, scalability, and big data sets.

There is a lack of advanced features such as SQLServer, PostgreSQL, etc. I would like to see minimum reporting services and analytics features in the next release.

MySQL doesn't have many tools to monitor performance and fix issues easily.

The graphical user interface needs to be improved. It would be nice to have drag and drop on tables to create relationships between them. Other relational databases have these basic features. It helps during development to have these on hand.

It needs improvement in high availability and scalability features. 

I've used the solution for more than ten years.

MySQL is good for small to medium sizes. Also, it has built-in security features. 

The scalability is good.

The support may be limited for users who are not on cloud and needs improvement.

Positive

We did not previously use a different solution.

MySQL is easy to setup and offers HA and scalability features. 

We implemented the solution in-house.

Its free open source availability provides good ROI. MySQL commercial version cost is higher than other open source databases. 

MySQL is free open-source software. This is the most valuable aspect for any company. 

We looked at an SQL Server and Mongo DB.

It supports wide range of languages and cross-platform support

Our organization uses MySQL as an ERP database for transactional and financial systems.

We are completely comfortable with the database’s performance and it is a mature product. My organization was looking for an open-source database for our smaller customers like the community edition. For bigger customers, we can scale into commercial and supported editions.

I would like to improve the solution’s pricing for licenses.

I have been using the solution for two years.

The solution is a very stable product. We have had no reason to be concerned about its stability.

The solution is scalable and it is one of the reasons why we chose the tool. Oracle has the information documented. We have a solution that we sell to the end users. There are about 50-200 users of that solution who may be using it simultaneously. We also have dozens of clients like that.

Our solution’s end-user customers contact us for technical support. We haven’t felt the need to contact Oracle’s customer support.

The technical preparation for our company to migrate from the previous database was about three months. We did our homework and shortlisted three potential solutions. We invested a month’s time to ensure that our solution could operationally run on MySQL. We also built migration capabilities to facilitate migration and rolled out upgrades to our customers. We never had any engineering issues during the implementation process.

We did the deployment in-house. Our company had the in-house skills to do it.

I would rate the solution’s pricing a six out of ten. The solution is not cheap but it’s a fair value. The pricing depends on the use cases of our customers. Some of our customers use the community edition which is license free and a good fit for their use cases. However, we encourage our bigger customers to sign up because of the scalability issues. The paid versions get direct technical support from Oracle.

I would rate the solution an eight out of ten. Our company is a service provider that has designed and built a solution. We sell it to other third parties. We are comfortable with MySQL. The solution being owned by Oracle and its brand positioning influenced a big part of our decision. The solution is very consistent with its peer group and we accept the solution’s range of functionalities.

We are happy with our choice. We evaluated over ten solutions before choosing MySQL. I am sure that we would be making the same decision if we were to do it all over again.