MySQL Reviews

I have been working for 25 to 30 years in this domain, and during this time, I have used various products such as MySQL, SQL Server, and PostgreSQL. Currently, in my product, I am using PostgreSQL, and in some projects, I am using MySQL. We are using the latest version of this solution.

We do projects for various government departments. We have used this solution for the transport department for vehicle registration, driving license, and all such things. We have also used it for port projects, depots, educational counseling projects, school databases, higher education, and health registry. As an organization, we have a lot of use cases of this solution.

It is very easy to install and has all basic database features.

We require more ease of use, scalability, and high availability. These are some of the critical features that we use and look for in a product. It should be easier to manage clusters. Scalability is very important for us because our projects and concurrency requirements are quite big. We also require high availability of the server, application, and other things.

It should also have more performance-based features or enhancements from the performance point of view. When we divide a database, it should be able to handle the queries very fast.

Whenever required, we also take support, but our people are quite experienced. They are able to manage it most of the time.

Its installation is quite easy.

We have our own people who do the deployment. We have various teams for various projects, and the size of the deployment team depends on the project. We have people who basically look after the DB activities, installation, and consolidation.

There is a licensing cost because we are going for a proprietary product. There are some other versions for which there is no licensing cost.

I would recommend this solution depending on the project. If a project requires the kind of features that are available in this solution, I would recommend this solution.

I would rate MySQL an eight out of ten.

The EER diagram is the most important feature for me as the EER diagram can show the inner picture of the database, such as the relationship between the tables very easily. We can also add, modify or delete EER diagrams very easily.

The user friendly interface which is easy to interact with such as creating backups, tables, views, and the EER model.

It has lot of options to interact with. Sometimes it is hard to find the appropriate options quickly. They need to add descriptions somewhere as to where a user can go to find the proper menu easily when required. Another problem is that since all the databases can be seen and operated together, it’s possible to make mistakes such as dropping the wrong database.

I have used this product for two years.

There was no issue with deployment

There were no issues with stability

There was no issue with scalability

The level of customer service is good. I understand sometimes they need to transfer the service to a knowledgeable person, so we need to have patience and explain the same problem several times.

The level of technical services is good. I understand the product is technical, so sometimes the reported problem requires more investigation.

I used phpMyAdmin. It is also a graphical interface but you have to buy the product while MySQL Workbench is free.

The initial setup is very straightforward. I didn’t face any problem at all.

I did the installation.

This product is good as it is a graphical interface. It's easy to do all MySQL database administration very easily. You just need to play around to be more familiar with it. The MySQL Workbench interface is well prepared to design a database including EER diagram, create table, and view very easily. The EER diagram allows the user to completely understand the database design, which is very important and useful for the people who are involved with the database. It’s easy to understand the inner picture of the database from the EER model.

We primarily use the solution for NDB and CG clusters.

The solution has made it easier for us to support our clients in India for a government technology project relating to CG clusters.

The IO segregation in CGE is valuable.

The auto-tuning and NDB cluster has some limitations regarding foreign keys. For example, when creating a partition with shared architecture data, the foreign keys do not work properly. Additionally, whenever we are working with this solution, as our projects are carried out globally, the size of the database is getting used fast. In case of replication and data access with two multiple sites or nodes to become a cluster, you need two separate data storage for accessing the same data from the two nodes. Hence, this consumes a lot of storage space.

We have been using the solution for five years and we are currently using version 8.0.31.

The solution is stable.

The solution is scalable, but I can configure this product with two nodes in case of a rack, but it is impossible in any of the databases. Therefore, I rate it a seven out of ten.

We do not have experience with customer service and support.

The initial setup is straightforward and it took less than twenty minutes. I rate it a nine out of ten.

One person is required for deployment.

I rate the solution an eight out of ten. The solution is good but auto-tuning and the NDB cluster can be improved.

We primarily use the product for small applications.

The solution is great for small applications in particular.

The performance is good.

The solution originally was designed as an open-source product. It has a community edition that anyone can use for free.

The initial setup is simple and straightforward. 

I have doubts about its overall stability. It's something that they should look at.

As an open-source product, there isn't really any technical support available if you get into trouble or have issues.

There isn't much scalability potential in the product.

I've been using the solution for a very long time. It's been years at this point.

The stability could be better. It's not as stable as I would prefer it to be. 

It was originally designed as freeware, as an open-source project, and the community wrote the solution. However, they've made it worse over time.

That said, the performance is pretty good.

The solution is not that scalable. It's not something you should pick if you need something to expand significantly.

While I can't speak to how many people use the solution in our company, I can say that it is used by several departments and divisions.

The solution is open-source and managed by a community. Therefore, there is no technical support available to users. 

The initial setup is very easy and quite straightforward. It's not overly difficult or complex. 

That said, I was not a part of the original setup and therefore cannot speak to how long the deployment took my team.

We didn't need any assistance from integrators or consultants. The setup was handled in-house.

The solution is open-source and free to use. We have the community edition. We don't have to pay to use it right now.

Right now, Oracle has taken over the business of MySQL. Now, it's standard that you have to pay money for the license. That's why we are shifting all our databases, the small, small databases, from MySQL to Oracle. We do have extra data, so we do require a license.

Currently, we are using the previous version of the solution. I can't speak to the exact version number, however.

I'd rate the solution at a five out of ten.

I wouldn't recommend it to other organizations at this time.

We use this solution for the database.

The connectivity with PHP is quite good.

It is easy to integrate, and the fees are less than Oracle and other services.

MySQL is good but it should be able to handle the large transaction levels that Oracle can. It should be able to manage large amounts of data. We have experienced some issues when we are handling a large amount of data in MySQL.

The memory consumption it's using is very high at times, and the default parameter settings are not quite good automatically. We need to tweak the configuration as per the requirements. This is an area that can be improved by giving some guidelines and direction. 

On the database side, it should be really lightweight, and the data structure should be like MongoDB.

It should put less load on to the memory and it should be able to handle maximum data.

I have been working with MySQL for approximately five years.

The solution is stable but there is an issue with memory consumption at times.

I have not contacted technical support. I am using MySQL with Zabbix and when I have an issue, I contact Zabbix who resolves the issues on their end.

I am a developer and I handle the other side of things. I rely on the DB team to handle the maintenance and deployment. My knowledge is very basic.

It's cheaper than other solutions.

For one level of data, you can use MySQL. However, for large amounts of data, you will have to find other databases.

Overall, it's a good solution.

I would rate MySQL a six out of ten.

I am a senior manager of the infrastructure team and MySQL is one of the products that I work with. We use it in an e-commerce portal. The database is light and everything works smoothly.

The performance is great.

This is a lightweight product that is not demanding on the resources, which is what I think gives it the edge.

We faced some details in clustering, although this may have been because we did not have enough knowledge about MySQL clustering. In general, an easier implementation for clustering would be an improvement.

The product is a little bit complex and it is difficult to find sufficient documentation.

We have been using MySQL for approximately six months.

We have not had any problems with stability.

MySQL is easy to scale.

We have dealt with Oracle support regarding other products such as Oracle Database and Oracle WebLogic. I believe that it will be of the same standard, although I'm not sure.

I am not a technical person but my understanding is that they are competent.

My complaint about them is that when we have a problem, we have to explain the same thing many different times to different engineers. Every time we engage with a new engineer, we have to start all over again. This is a nightmare that we chased three months ago.

In addition to MySQL, we use Oracle and Microsoft SQL Server.

Oracle is an enterprise-level product but it is very straightforward to install and it has sufficient documentation and guides, which we did not easily find for MySQL.

Implementing clustering depends on a few different layers or different components. The clustering layer handles requests from the applications, and it is all a bit more complex than Microsoft SQL Server or Oracle.

The design, review, and deployment took approximately one week.

At the moment, because of the issue that we are having with the clustering, I may not recommend MySQL. It would first need to have the clustering problem fixed and then have a sufficient deployment guide. 

I would rate this solution a seven out of ten.

• Relational database (Although it's not 100% compliant with Standard SQL)

• Performance

• Open Source

• Ease of setup and use

• Ease of use with PHP, Python, and Java

Using MySQL helps to keep the costs down. With immense material available on the web, training is easy too.

This is the de facto DB for web development with PHP. If you worked with LAMP environment, this was the M in it (others being Linux, Apache Tomcat and PHP). With open source products, development was a breeze. Overall, this is a boon to small to medium database applications.

The simplicity of the product lets people abuse it. I've seen so many people create tables and add indices in PHP code. Some of these web developers only know some things about the database.

I have used this solution for about eight years.

We did not use a different solution for the applications that use MySQL. I mostly use Oracle for larger, enterprise software.

The initial setup was straightforward. There are a number of Open Source tools, including Toad and MySQL Workbench which helps with configuration and use.

This started as Open Source project under Sun. With Oracle acquiring Sun, MySQL is now owned by Oracle (not the community). Oracle promised to keep it open sourced, but the community is not convinced. So, there is a branch that's called Maria DB that's slowly taking over in some Open Source projects.

That being said, it is still an Open Source product and it is free to use under GPL license. This means you can always, get community support. But, if you want Oracle's support, that is not free.

If you use it in enterprise applications, you may have to purchase commercial license from Oracle. Here is a couple of links that discuss various options:

http://white-paper.b-lay.com/o...

https://www.linkedin.com/pulse...

We evaluated MS Access, SQLite, PostgreSQL, FireBird, and Oracle.

This is a relational database tool for small to medium sized applications. However, this didn't start as a Relational DB, so if you want a truly Relational Database for an Enterprise, similar to Oracle, you may want to look into PostgreSQL, as well. However, MySQL is still a very good database for internet based applications.