MySQL Review

Provides a simplistic view for building custom queries and has less performance overhead

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using MySQL for three months.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More MySQL reviews from users
...who work at a University
...who compared it with Oracle Database
Add a Comment