MySQL Reviews

We are developers working on different types of projects. We use relational databases in some projects and non-relational databases in others. When we use relational databases, we use MySQL. When we use non-relational databases, we use our DynamoDB or MongoDB.

1. Ease of Use: MySQL is relatively easy to set up, configure, and manage, especially with tools like MySQL Workbench and command-line utilities. Its widespread popularity also means there is ample documentation, tutorials, and community support available for users.
2. Open Source and Cost-effective: MySQL is open-source software, which means it is free to use and can be customized according to specific requirements. This makes it a cost-effective choice for startups, small businesses, and projects with budget constraints.

Compared to some other database systems, MySQL may have limitations in terms of advanced features and functionalities, especially when it comes to complex data relationships and transactions.

I have been using MySQL for two years.

In my past two years of MySQL experience, I found no bugs or breakdowns. It works completely fine.

Many cloud providers offers managed mysql service with scalable architecture ,automated backups , monitoring and scaling. Leveraging this can solve the scalability problem.

MySQL is very easy to install and use.

As it is an open source and there is community edition available so if you have small or medium use case it is much cheaper to use.

Below are some thing to consider while working with mysql.

1. Regular maintenance 

2. Security consideration

3. Version compatibility

You can try MySQL if you have any use cases of relational databases. It is very easy for somebody to learn to use MySQL for the first time. The solution worked fine for me, with no breakdowns or scalability issues.

Overall, I rate MySQL eight and a half or nine out of ten.

I like the simplistic view of MySQL to build custom queries and things like that as compared to SQL Server, which seems more cluttered.

SQL Server has a query analyzer. MySQL pretty much does the same, and performance-wise, it has less overhead for connecting to our ERP system. It seems more responsive and cleaner. With MySQL, you get what you need without any overbloating, for which Microsoft is known. That's why they have so many constant security patches for everything because there is so much stuff, which degrades performance.

The GUI interface probably can be improved. Let us say I want to see the relationships in the database. In the query analyzer, I would like to go and drop the tables and create relationships between the tables. I haven't found a feature like that in MySQL. It was a shortcoming even in SQL Server.

MySQL can have more performance monitoring tools. I know Google has these tools, but within MySQL, there are not that many tools to monitor things like performance and database locking. They might be in there, and I might not be familiar enough to know where they are. I am a pretty new user of MySQL.

I have been using MySQL for three months.

It has very good stability. We haven't had any issues with it.

It has good scalability. You can use the Google interface to build it on the cloud. If you start noticing performance issues or you see it taking up memory or resources, you can add another processor. It is pretty easy to do. Right now, we are in beta. We haven't rolled it out completely to the people.

I haven't had to use their technical support. They have plenty of online resources. If you have any problem, you can just search for it and find the answer. Somewhere, someone has done it before.

The ERP company that we work with is moving away from SQL to MySQL. From my understanding, it is because of the cost. MySQL is also more streamlined and gives them what they need. 

Even though I am a SQL Server person, MySQL has come a long way from what it used to be. They have made great strides. It seems like Google is moving more and more to it. In Google Data Studio, which gives you an interface to build dashboards, when you try and connect to new resources, you will notice they prefer MySQL on the cloud or a private server. Google is leaning more towards the MySQL side of things, and they make it very easy. It is a lot more work trying to connect to SQL Server. MySQL seems to be the preferred cloud database that people are going for.

The initial setup was straightforward. MYSQL installation has fewer options than a SQL Server installation, which has endless options. MySQL installation is more straightforward and streamlined. It doesn't have a lot of extra features. It is just a database. It is a database engine that gives you what you need, and I like it.

I am doing one installation right now on Google Cloud. I am building an instance of MySQL. It is just more simplistic. It is more to the point and what you need. In SQL Server, you need to dive into the endless options, and you use maybe 60% of what is there. There is a lot of stuff that people don't use, which you end up uninstalling because it affects the server performance, and it is a service that you are not even using. There is a full install as well as a custom install with SQL Server. If you go for the full install, it throws everything into the server, and you start noticing performance issues. Then you realize that there are services that you are not even using. Some places don't even use analytics or reporting services.

Microsoft licensing for SQL Server is probably ten times more expensive. I used to work for the government, and I remember when we were looking into upgrading to the enterprise version of SQL Server 2019, the licensing was going to cost 350,000. To get the equivalent in the cloud, it was going to be about four grand to get the same processing power and everything else. With MySQL, it was going to be about 300 for the same licensing. 

Cost-wise, for sure, there is a huge difference. Would you prefer to pay 300 a month or 3,000 to have the same amount of data resources? You might lose a few options that you need, but it isn't worth the price difference.

If you want just a database for data storage, I would recommend MySQL. If you want something that has everything in it, such as reporting services and analytics, SQL Server might be better. Cost-wise, MySQL is almost pricing itself out.

I would rate MySQL an eight out of ten for ease of use, especially for someone who has never used it and implemented it. It was pretty straightforward to implement it. It gives you what you need. It surely provides the basics such as data storage, setting up the tables, etc.

MySQL is an open-source relational database management system used to store data.

MySQL is an easy-to-use solution that provides stability, reliability, flexibility, performance, security, and high availability.

MySQL could introduce more indexing strategies. There are a couple of strategies where you can index things to be more searchable and visible. We lack that kind of functionality. For example, if your name is indexed correctly with a certain strategy, it can improve the search results faster. The solution’s interface could be improved.

I have been using MySQL for my entire career.

MySQL is a stable solution.

MySQL is a scalable solution.

The solution’s initial setup is easy.

MySQL is a free and open-source solution.

MySQL is deployed on the cloud in our organization. Big companies like Netflix, Uber, and Facebook use the solution. Since MySQL is an old product, many people might have faced similar issues, posted them online, and got a resolution. MySQL's performance and scalability features have supported our database growth.

New users can follow the documentation to use the solution, as it is straightforward. You need to be very clear about why you want to use the solution. MySQL is a relational database management system that cannot be used as a dynamic database management system.

MySQL is generally faster and more efficient than other relational database management systems. Hence, it is our preferred choice for applications that require high performance.

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

I would use MySQL for a medium project, with around 1,00,000 hundred thousand users, because of the indexing and stored procedures.

MySQL's performance needs to be improved for enterprise-level applications compared to Oracle and Postgres. That's the only drawback I found in MySQL. When the table storage is full, the solution's performance becomes slow. The solution's security needs improvement as DB2 is more secure than MySQL.

I have been using MySQL for more than ten years.

MySQL has good stability.

I rate the solution a six or seven out of ten for stability.

Around 150 users are using the solution daily in our organization.

I rate the solution a six out of ten for scalability.

We previously used Oracle. We switched to MySQL because Oracle's license was costly.

It's really easy to set up MySQL. On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

We implemented the solution in our organization through a consultant. It took a few hours to set up everything. Around one to two people were needed to deploy the solution.

MySQL is a cheap solution.

When you compare Oracle and DB2 with SQL Server and MySQL, all these come under RDBMS (Relational Database Management System). Since the licensing for Oracle and DB2 is costly, people will go for either MySQL or Postgres. People go for MySQL because it is better than Postgres in indexing and supports multiple data types compared to Postgres.

Just one person is needed to maintain MySQL. We didn't face any challenges using MySQL because of many open communities. If you have MySQL's commercial license, you will get good support. I would recommend MySQL to users who are going for medium enterprise applications.

Overall, I rate the solution a seven 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. Also the newer versions of MySQL offers lot of new features. 

We use MySQL in multiple projects for storing, task management apps, and dating apps.

MySQL is the best option for the Laravel PHP framework. It supports multiple model systems, and it's very easy to call MySQL compared to other languages like MongoDB. I prefer MySQL for the Laravel PHP framework.

The solution's security features depend on where we host our server and database. We have some preventive measures to reduce attacks. We have taken authentication and only allow a particular IP address.

In MySQL, we need to define every table beforehand.

I have been using MySQL for four to five years.

In MySQL, we need to define every table beforehand. However, we don't need to do so in MongoDB. We can add a new row or column in MongoDB anytime, making it much easier. If you purchase MongoDB's plan, it supports many security features, and you don't need to check about security. They will handle everything.

The solution’s initial setup is very easy. For the first time, the solution's implementation will take some time. However, you can use it multiple times after you configure it.

MySQL is a cheap solution.

Maintaining the database is a task. We take a weekly backup for each database so that we can upload it to the server if anything happens to the data. We created a cron job so that the data can be taken and then uploaded to a specific space so that we can go back to the particular big data whenever we want. I prefer MongoDB for scalability because it's much easier to maintain MongoDB.

Just one person is enough to maintain the solution. The solution has good documentation available on Google.

Overall, I rate the solution six and a half out of ten.

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.

The solution is a database server. You can use it for desktop or web applications. The tool is used mostly for web applications. Most websites have MySQL databases behind them.

MySQL is an open-source product and has good community support. If you encounter any problem, you can easily ask other members of the community to help. They help you a lot. On top of being free, MySQL is a cross-platform database, meaning it can work on both Windows and Linux. It is very good for us.

The solution’s stored procedure is too light. MS SQL server supports stored procedures which MySQL doesn’t. Oracle and MS SQL servers support treiber which notifies you about data changes in the database. MySQL doesn’t support treiber.

I would like to see the automatic backup feature in the solution as well. Data is very important and we need to preserve it in a safe place. It would be good if MySQL can back up the data automatically.

I have been using MySQL for ten years. I use the solution’s latest version.

I haven’t seen any problems with the solution’s stability and I would rate the stability a ten on ten. It is a very stable tool.

I would rate the solution’s scalability a ten on ten. The tool is network-based and the scalability depends on the design of your project. You can use the product of both large and small-scale projects.

We are not a very large organization. There are around ten developers who use MS SQL server and MySQL for databases.

We are simultaneously using the MS SQL server and MySQL server. We first used MS SQL server and then in some projects, we required free and open-source databases. We use MySQL for those projects.

The installation was very easy and straightforward. The setup took around a couple of minutes which was five to six minutes to complete. The tool’s installation was really fast.

We didn’t require any assistance from third parties.

My company must have seen some benefit with the solution’s use.

I would rate the overall solution a nine out of ten. We didn’t find any issues in the solution’s maintenance. In every project, one developer would be in charge of their respective database maintenance. The solution has large community support.

MySQL is a fast database that is also high performing. When you want to do a project that requires a fast transaction, MySQL acts very well there. When a company needs a free database that is fast, could be connected over the network with many people, and do transactions, we usually suggest this solution.