MySQL Room for Improvement
As for what can be improved, right now we don't use the MySQL cluster. There is a MySQL cluster that you can run in a standalone mode, like a single database or you can do it in a cluster master-slave implementation. The cluster is not the best when it comes to MySQL. That's why we switched to MariaDB. For that simple reason that the cluster there is better. It's more manageable and it's easier to work with.
We decide what to use depending on the needs. For example, if we need to mount something in a cluster mode, we use MariaDB, which again, is a Dockerized solution with a Helm chart as well, and it's very easy for us to deploy and manage, and also to scale when you just increase the number of slave versions. So MySQL doesn't have that great support when it comes to clusters. You can definitely use MySQL for that too, both support clustering, but the MariaDB is better.
Additional features that I would like to see included in the next release of this solution include better support for backups. Because if you go with the MySQL Percona version, it gives you the tools to back it up securely. The vanilla version of MySQL doesn't have that. It actually does have it, but it is just really poorly executed. I would improve the backup system as well as the encryption. To make it smoother right now takes too much work. It should be a little bit smoother to backup the encrypted data the way you want it and have the ability to push it anywhere you want. That is not part of it right now.
Now it is a database, so you don't know what you're going to do with it. It's difficult. You're just going to come up with solutions. But I think you can generalize here and come up with really simple solutions, which we have already in MySQL. That's probably the one thing that I would try and push right now for people to switch. But people are still not biting, because if you go with the managed version, then all the backups are taken care of for you by Amazon or Google or Microsoft. Then you really don't care. But for us, since we're doing it locally, self-hosted, we would like to have better tools for locking up the data.
Right now, one aspect that is also linked to backups is running things in a crosscheck with semi-managed solutions. This requires a bit of a context. Since we're running things within the clustered communities, we're kind of pushing the Cloud into the cluster. We also want to push some of the tools for the database into a cluster, as well. So these are what we call Kubernetes operators. And there's MySQL operators that were first developed by the community. Those kind give you the ability to backup data within the cluster. So now you have a fully managed solution running from your cluster. These are called MySQL Kubernetes operators.
We are looking into those right now to upgrade our solution, which would mean that we can just execute our backup natively within Kubernetes, not via special scripts. This would make it much easier to actually deal with any kind of MySQL issues within the cluster, because it would be cluster-native. That's what the operators are for.
I think Oracle just created a really good one. It surprised me that they have this. It's not because of Oracle, but they got pushed by the community and actually created the MySQL Operator for Kubernetes, and that's what we're moving towards.
This is going to give you an ability to have a cloud-managed solution within the cluster. And then you can ask the MySQL Operator for the database. They'll partition the database and give it to you. So it will change the nature from you deploying it to you just asking the cluster to give you a database. It's a fully managed solution right from the cluster.
So that's what we're heavily looking into right now. We'll be switching to using Kubernetes MySQL Operators. It's a high-availability cluster running within the Kubernetes cluster.
Right now we're pretty good with that. It's working fine. We're trying to find some time to actually release that globally everywhere. That's where I am right now.
But in terms of technology, if you give up Oracle, you just go to a MySQL operator. That's the one we're using, what we're actually looking at - to create, operate and scale mySQL and sell it within the cluster. This idea of having a cognitive MySQL becomes much easier to manage within the cluster, as well. So you don't have to go with the cloud solution with AWS or Google cloud or Amazon MySQL or the Microsoft version.
The Oracle SuperCluster is the Oracle MySQL operator. That's what we we are looking into a lot right now. Mainly because it does backups on demand - it's so easy to backup. You can just tell Kubernetes to backup and you don't have to run special scripts or special extra software or codes to back it up. You can make the backup as you would do anything else. Send a backup or some other data source or insert an Elasticsearch into it here. Just say "Kubernetes, back it up" and you know Oracle has this adapters within the cluster to back it up for you taking increments or different companies. So that makes it really nice and easy to use and to deploy.
With that kind of solution you can ask to class or petition the database how you want. So again, it changed the nature of the kind of push-to-pull second nature system. Are you pushing your containers to a cluster? You just say cluster, "give me a database" and the class gives you the base partition database, creates a database in a secure manner, gives the connection to the database, and you're done. Then you can back it up on a schedule on to any backup switches. It's much easier. So once this goes, it is going to be widely adopted, which it should be. But I think people might not have the tech skills right now. But once it's adaptive, maybe in a few more months, it's going to be the number one solution for everybody.
In terms of what I'd like to see in the next release, one thing that's always missing is dash boarding. There's no real BI tool for MySQL, like there is in Yellowfin and all the different tools that you get. They all have MySQL connectors, but there's no specific BI tool for MySQL. Open source projects have sprung up, but they're more general purpose, like Postgress, a MySQL kind of database, a relational database. I don't see any really nice tool like Cabana for elastic searches that I can tell clients to use because it would be too technical for them. They would have to have more technical engagement with writing the course, drag and drop, and creating a graph like in Power BI where you just connect with DIA.
So I'd like to see the grab and drag and drop tables, nice beautiful graphics, and pie charts. You don't necessarily have that with MySQL like you have other solutions, which are really cost prohibitive for some clients. It'd be nice to have an open source solution for that. Decent solutions. I mean decent that I can take to clients. It's so technical. They want to drag and drop.
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.
View full review »The workbench could be improved. In particular, error messages can be improved, which are horrific and completely unhelpful. I'd like to see improved parsing of errors. When you write SQL and it crashes, it usually is something completely irrelevant and not helpful. I've started to use GPT 3.5 for finding out how to do things. I got to do something a bit different, and that I found to be very useful. If there was some way to tie it into one of the new AI tools, that would probably be a good idea. There were a couple of things that I've found difficult to do in the past, and I remember they were fiddly. I set them into ChatGPT, which is GPT 3.5, and it gave first-class answers.
I find it clunky. It just doesn't feel very modern. It feels as if you have to go through multiple steps to get to places, and it's not clear, but operationally, I find it fine.
View full review »Buyer's Guide
MySQL
March 2024
Learn what your peers think about MySQL. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
767,995 professionals have used our research since 2012.
Improvements to MySQL depend on the specific use case. For example, in my scenario, I frequently need to maintain and store data, which can then be utilized to generate reports. On the other hand, others may suggest incorporating a feature that allows for easier visualization of the data, such as what is available in Power BI or other similar tools.
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.
View full review »RU
Ravi Upadhyayula
Senior Consultant at Tata Consultancy
MySQL lacks a feature akin to Oracle's Real Application Clusters, which ensures continuous database availability within the same data center or nearby data centers. Without this capability, MySQL's suitability for mission-critical applications is diminished. Until MySQL incorporates a similar feature at the application level, its appeal for high availability remains limited. Historically, we've relied on external security measures for data protection, such as encryption. However, when encryption methodologies are employed within MySQL, there may be a slight performance degradation due to the computational overhead associated with processing large volumes of data in the database.
View full review »While utilizing a comparable algorithm, is noted to be sensitive, especially when configuring the inner device. If DCDR is not properly recovered from NDC, it can lead to system slowdowns. There is a need for enhancements in the InnoDB cluster, specifically the capability to support more than two nodes in MySQL. Additionally, the inclusion of data nodes would be a valuable improvement. For users new to the system, it might pose a bit of a learning curve.
View full review »There should be an arrangement for end-users to get trained to use the tool. End-users don't know many things which MySQL offers to its users. So, there is a need for the end-users to upgrade themselves. Also, the tool is already good the way it is currently owing to its features like multithreading which helps with the queries quickly. In short, if one goes for the complex part, if one uses it for a very specialized case, then that person needs to write a very complex query involving multiple tables, multiple joints, and multiple conditions based on whatever scenario one uses.
Improvement-wise, a graphical interface could be added for new users, eliminating the need to memorize the complex syntax.
View full review »I would like to see more integrations of the solution with other platforms and improve the support on different data types.
View full review »The integration with other systems can be improved as can the integration between other databases. We have a workaround to integrate it with other systems but that can be improved.
In the next release, I would like to see better day-to-day support in case we face any issues.
GG
reviewer1432350
Computer & Information Systems Manager at a real estate/law firm with 51-200 employees
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.
View full review »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.
View full review »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.
View full review »The tool needs to improve table visualization.
View full review »AB
reviewer2089122
Associate Consultant at a computer software company with 501-1,000 employees
Clusters are hard to perform so we use no SQL alternates like MongoDB.
The solution should manage large data sets better because data that is around one lakh or two lakh fails to load. In these cases, we use no SQL structures like MongoDB.
View full review »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.
View full review »JK
James Kulundu
Data Analyst at KPMG East Africa
The full-text search feature must be improved.
View full review »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.
There is room for improvement in terms of the stability of the solution.
View full review »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.
The solution is expensive.
View full review »SG
Satishbabu Gunukula, Oracle ACE
Works
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.
View full review »CG
CharlesGuise-Brown
Clinical Data Management Principal at Vertex-in-Healthcare
I would like to improve the solution’s pricing for licenses.
View full review »CN
reviewer937698
Principal Software Engineer at a manufacturing company with 1,001-5,000 employees
The availability of tools could be improved in the MySQL open-source platform. They can provide more analytical tools. I haven't had any particularly difficult issues to troubleshoot on MySQL, but in the past, on Microsoft SQL Server, I had to troubleshoot some difficult issues, and better tools were in place to see what was going on in real-time on the server. So, that's the bit that is lacking on the MySQL open-source platform.
At times, the autoscaling does not happen when there is a surge in load. We had to depend on manual scaling. It led to website crashes in the past.
View full review »AJ
Amos Babatunde Jayesimi
Officer IT data processing at Stanbic Bank Ghana, Ltd.
There should be a training platform for the solution without the complexities of owning a server partition in our system.
View full review »ND
reviewer1456815
Specialist Geosciences Data Consultant at a energy/utilities company with 10,001+ employees
I would like to see an autocorrect option, where if you're typing a query and you enter a comma instead of space, or something similar, the ability for it to be able to understand based on your previous scripts would be an advantage. For example, if you were to put a comma between your AND statements then it's not going to work. Maybe a smarter application where, as you're writing queries, similar to the way that grammar and spelling are checked when you type a text message on an iPhone, it could be autocorrected.
I would like to have the ability to cancel a query in SQL Developer. Specifically, I would like to be able to cancel the query should I accidentally write one that's going to loop, or have a JOIN wrong, where you get millions of records joining with millions of records over and over again. The availability to hit cancel so that it doesn't keep running would be helpful because, when such a thing happens, then you have to shut down the whole application and you lose any queries that you might've typed before.
View full review »The user interface could be more user friendly. Mainly because most of the times we see black and white digital lines. Something like Python.
View full review »The backup methods need improvement. MySQL needs to improve its backup methods so that you can actually do a backup without affecting products. Currently, when you're doing your backup, it locks the database. When someone tries to access it during a backup, it fails to read or to update. They can improve on the backup and all the backup features in general.
View full review »Although MySQL should cover most of the needs of an average user, there are constrains that need improvement.
For example, MySQL doesn’t support check constraints. MySQL’s performance is not optimal on subqueries and can significantly increase the server load for database intensive applications.
Another issue is the ineffective table manipulation during multiple transactions which result in implicit Commits.
Finally, since MySQL is now part of Oracle, and Oracle already sells their own databases, changes and bug fixes have significantly slowed down for obvious reasons. Oracle cannot improve MySQL too much, since it will then compete with their commercial database systems.
View full review »The GUI could improve to make MySQL better.
View full review »The GUI could improve in MySQL.
View full review »NM
reviewer1378032
Database Engineer at a retailer with 10,001+ employees
The developers of MySQL, which are Oracle MySQL, Percona, and MariaDB, seem to not be focusing much on object-oriented replication. Basically, replication is based on a text level of replication. There is a text level replication in Oracle, that is so similar it can be implemented in MySQL, however, it needs to pull a lot of resources. They have altered their approach for replication. Still, more focus on object-oriented replication would be good.
They should come up with a better solution than the NDB cluster for better scaling. If they could come up with a better solution for write scaling, apart from the NDB cluster, which is supported by all open source communities, that would be great. Although the NDB cluster, is an open-source tool, it's not widely supported as a solution.
The latest 8.0 version has come up with whole new features.
View full review »AG
Arief Gunawan
Product manager at Metrodata Electronics Tbk PT
In terms of what could be improved, some of the features that Oracle has, MySQL also has. Like if a customer is looking for a high availability solution, a security solution, a monetary solution, they can have all that in an expensive product like Oracle but they can also have it when they're using MySQL.
Every product has their own pros and cons, and also has their own market. So if the customer is already using or has already used Oracle for a long time they will know the look and feel and the character of this database that can fit into their business.
They will not choose MySQL over Oracle if they already know about Oracle. But if they start to build a new application before they are creating a secondary application then they may not be familiar with Oracle and they will try MySQL. Maybe they will like it because they will see that this database also has complete features. If they try Oracle they find the same features but different pricing. In certain things, MySQL cannot have the same benefits as Oracle but for some customers who are already using Oracle, you're not going to move to another product even if it's more expensive.
And MySQL is a cheaper product.
That's why I say that MySQL has many of the same features as Oracle. Both of them have high security.
The customer that comes from a small or medium business will prefer to choose MySQL rather than the Oracle database because they already know that this product is best for their business because it is not expensive compared to Oracle.
Oracle does have different versions with different prices. The cheaper is called the Standard Edition. And the most expensive is the Enterprise Edition.
MySQL is comparable to the Oracle Standard Edition if we compare peer to peer. But the difference is that the Standard Edition doesn't have features like the Enterprise edition. But the high security and the high probability are not in the Standard Edition. But MySQL will have it. It will have all those kinds of features with a lower price. Because the Standard Edition is more expensive than MySQL.
Every kind of enterprise company has a core application on which their business depends. Mostly they will just choose the Oracle database. Why? Because of Oracle database's capability to handle the big workload for enterprise businesses. I think that will become their priority and MySQL will not be an option for them.
But someday I would like to see the enterprise companies changing their mindset. If you are talking about core applications related to the high workload in the future, they can choose MySQL as well. Maybe not now, because right now they still see MySQL as for small/medium business and not for the enterprise business. But I hope in the future MySQL can be seen as on the same level for their database.
That will mean that all enterprise companies can have two options when they are choosing a database solution for their core application; either Oracle database or MySQL.
The weakest link is replication. MySQL’s replication is touchy and doesn’t support master-to-master setups.
MySQL’s replication was implemented by playing back SQL statements getting executed on the master database node. That means if a slave node gets behind, it has to catch up by running every SQL query that has executed on the master. When the slave gets too far out of date, it is unable to catch up because the replication log is lost.
Master to master replication is used to allow writes to either node in the cluster (INSERT, UPDATE, DELETE). Since MySQL does not support this, you can only safely send SELECT queries to slave nodes. If you run an insert, update or delete against the slave node, then it is out of sync with the master and may break if a later replication event comes from the master on the same table.
Nowadays, I use phpMyAdmin or MySQL WorkBench to manage MySQL. I would have been in a position to comment on what requires improvement if I had spoken about the tool three years ago. There are no improvements needed in the UI of the solution since many tools in the market help the user get the job done. MySQL WorkBench belongs to Oracle.
The performance, stability, and security are areas with shortcomings in MySQL, where improvements are required.
It would be a great improvement if the product could be made affordable enough for me to be able to access support from MYSQL, especially when I deal with mission-critical applications.
AV
Andre Visser
Technical Director at Metrofibre Networx
Since we started the development, like, three years ago, it's just been improving, so there are no areas that need to improve. It is easy to use.
The licensing cost of the solution is expensive, which MySQL needs to consider improving.
View full review »This solution needs to be improved when it comes to working with desktop applications on the developer side.
View full review »AM
Ariful Mondal
Global Data Architecture and Data Science Director at FH
Typically security will be on a security layer. I haven't really looked into the security of it, but it should be good.
It could be more secure.
View full review »The replication needs improvement. It's becoming a native cloud product like Oracle DB or Cockroach DB.
View full review »SJ
reviewer936300
Director Of Sales Marketing at a energy/utilities company with 10,001+ employees
It would be ideal if the solution had more references available in terms of helping me find answers to issues or problems. When I run into issues, I really have to research how to fix them.
The installation process could be better.
I would like the product to have even better stability and scalability.
View full review »Sometimes, I get lost in the toggles and buttons, and a better visual design would be nice. The layout is not user-friendly or efficient.
I would like to be able to sort the data easily without having to do a request to get the table out of the database into the web page. At present, I can't do it directly inside MySQL; I have to do a request and print out my request into a web page.
View full review »PA
reviewer1769190
Software Engineer at a financial services firm with 10,001+ employees
MySQL can improve some of its functions. However, it is dependent on the use case. For example, if we are having multiple database connections in this tool, and we are performing one operation in one database, it takes a lot of time due to the reason we are selecting and processing the data. When we have a lot of data it takes a longer time. The transaction gets stuck in a queue and if we try to stop that particular transaction, it won't abort until all the selected records have been processed. This sometimes can be a lot of time and it can hold up our live processing of transactions. This product should be able to handle multiple processing at a time.
In an upcoming release, there should be something added similar to EPL. For example, when using the flow diagram, we can create a schema. We have two useful features to add or create the table, but there should be some UI features to allow us to drag and drop to create other schemas. This would be very helpful.
View full review »LK
Lawrence Katuruza
Systems Administrator at Dairibord
MySQL could be improved by adding more automation. There are no additional features I would like to see that I can think of at the moment.
View full review »AC
goforitandy
IT Consultant at Woohoogeeks
MySQL tutorials and guides could be improved. Often they are too complex for someone with no database experience to understand.
It is not an easy database to learn for the novice, and very often users need to take a course, employ the use of an online tutor, or IT professional to assist. Also, it is known that it is often difficult to locate guides for specific functions for developers.
It might be good to have some way of creating web services easier, rather than having to write a User Defined Function (UDF) in PHP.
View full review »I would like to see some improvements in the solution’s integration aspects.
View full review »The two most common and popular MySQL database engines are MyISAM and InnoDB. Database engines provide the underlying functionality for MySQL to work with and process data. MyISAM is the default engine for MySQL for versions earlier than 5.5.5 and functions well in most scenarios.
However, depending on your needs, there are situations where another database engine, such as InnoDB, may be the better choice. For example, InnoDB supports transactions, whereas MyISAM does not. InnoDB also provides support for foreign keys, whereas MyISAM does not.
When it comes to supporting big data, there is space to improve upon the database engines that are supported by MySQL. An example of this is the Vertica DB engine (https://en.wikipedia.org/wiki/...), and offering support for it would be valuable.
View full review »AM
ARJUNMarya
Enterprise Architect at a computer software company with 1,001-5,000 employees
Rather than going in-depth about the technical features, which a technical person can directly tell, I would say that MySQL should be able to adapt to the next framework. The 5G framework means an unstructured framework. So if MySQL becomes smoother and more adaptable, it'll be easier. In terms of new features, automation is always the biggest demand from our customers.
View full review »PJ
reviewer1461639
Deputy Director General at a computer software company with 1,001-5,000 employees
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.
View full review »RP
Rehana Parvin
Database Administrator at a recruiting/HR firm with 1,001-5,000 employees
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.
View full review »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.
View full review »AR
reviewer1620885
Vice President & Head of IT Governance at a financial services firm with 1,001-5,000 employees
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.
View full review »DB
Deepak Bansal
Founder at Art World Web Solutions
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.
View full review »HE
Haitham Elwany
IT Infrastructure & Data Platform Sr. Manager at a financial services firm with 1,001-5,000 employees
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.
View full review »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.
LM
LeonMofor
Ingénieur Etude et Développement / Technical Lead Java at ATOS
I would like to see a feature added to be able to handle high availability, which would allow us to scale the database or the system on many platforms.
Scalability has to be improved, as you have only one instance of the application, or two, or more instances at max that are connected on one instance of MySQL.
In the next release, I would like to see the scalability features improved to allow you to configure it and reduce the complexity with the configuration, making it easier for the end-user to scale. Make it as simple as it can be.
Add the possibility to define custom data types
Add OLAP and backup capabilities
View full review »TB
reviewer1788699
Managing Director at a financial services firm with 201-500 employees
Even for the best database, we always want the database to perform much better, so we wish MySQL would be much better, in terms of performance. When they release a new version, they mostly concentrate on scalability and performance.
View full review »KV
Karel Van Der Walt
Data Architect at ACPAS Loan Management Software
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.
MM
Muhammad Nurazhan Moin
Senior Web Manager at a university with 501-1,000 employees
It would be helpful if there were a graphical user interface to administer, configure, and tune it.
If it had something similar to Microsoft’s DTS engine then it would be the best database system out there.
View full review »SN
SaifNan
Director at BAB
The interface could be improved.
View full review »PE
reviewer1621470
Lead Project Manager, Owner at a tech services company with 11-50 employees
In terms of what could be improved, there is not anything that I can think of offhand.
Everything related to automation or improvements are external tools that are brought into it, so it has nothing to do with the robustness of the system itself - it is the developers and implementations that touch it. Those can be improved, but MySQL itself is fine as is.
I would just say that it could be a little bit simpler to use.
View full review »ZG
ZelalemGedefie
Senior System Administrator at Debre Markos University
The solution could have better integration and security features.
OK
OmidKoushki
Solution Architect at KIAN company
The solution could improve the monitoring. At the present time, you need to use third-party monitoring solutions.
View full review »HP
Hetul Patel
Senior Data Analyst at Charutarhealth Org
It should have some code analytical functions. It can also have a monitoring tool.
View full review »AR
AlmiroRocha
Information Technology Infrastructure Manager at a comms service provider with 201-500 employees
I would like to have features that allow us to jump between the cloud and our on-premises system.
View full review »HT
Haim Tzadok
Co-Founder/CEO at Grigale LTD
SQL and NoSQL use.
View full review »I would like to see additional side management tools and IDEs.
View full review »Replication and HA features, but that is to be expected at this entry point
View full review »VC
reviewer938061
Sr. Solution Architect at a computer software company with 5,001-10,000 employees
Integration is a key feature in need of improvement, as we have spent hours building this just to ensure that a set of data is exposed to a different client, a different world in need of that data. Since we are dealing with open source, which we are now employing in memory databases as well, it would be nice if they were to start thinking along those lines.
YT
YongSheng-Tang
Unemployed (previous role was Solutions Specialist, System Integration)
Because I am the middleware guy I'm not the SQL database administrator. If I have any issue with it, I'm going to contact the right person. Sometimes, not because the version is not the latest version, there are some issues with it. Sometimes there's an issue with the server which creates issues with it. Then, when the administrator checks the status and makes notes, it works normally and the problem is fixed. With a big company you are not going to work directly with the MySQL database. We are the end user and not the administrator of the SQL database.
For MySQL, in terms of the usage or as the end user, I don't have much to recommend, as long as the query latency meets your requirements, it will be great. Otherwise, it's the horizontal scalability and you get more parallel in the implementation in terms of the SQL database regardless of the usage. This is probably much better than the vertical in terms of scalability.
View full review »PN
PareshNayak
Oracle Cloud Infra Architect at Wipro Limited
We want high availability and replication features, which are currently missing in this solution. It would be great if they can provide an in-built replication feature, similar to Oracle RAC, in MySQL.
View full review »HC
Hector Cuna
Sysad Database Administrator Lead at USSC
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.
View full review »MR
reviewer1442025
Senior Database Administrator Engineer at a comms service provider with 10,001+ employees
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.
View full review »RS
reviewer1252344
COO at a tech vendor with 1-10 employees
The analytics features are in need of improvement. They aren't as far along as the capabilities that you have in terms of analytics for SQL Server and Oracle.
View full review »It does not stand out regarding scalability. When the company size increases, the user base having actual experience with (very) large MySQL solutions is reduced.
View full review »Security is a concern. MySQL could have better security features.
View full review »DO
reviewer1139685
Business Intelligence Manager at a translation and localization position with 501-1,000 employees
What it would compare it to, from my point of view would be, Microsoft SQL Studio. I find the Microsoft solution a bit better. But mostly in terms of the UI layout, I would say. I just find it a little bit more efficient. But to be honest, I can work equally as well with both.
View full review »We haven't noticed and features that are lacking.
From a user perspective, the initial setup could be simplified a bit.
View full review »I think that the stored procedures and the development tools to write and debug large queries could be improved.
View full review »CR
reviewer1650315
Senior Java Developer at a computer software company with 11-50 employees
Since we upgraded from 8.0.12 to 8.0.22, it has had some slowness-related issues. Some of the queries that were fast previously are quite slow now. I did some research, and I found many people complaining about it.
View full review »From where we are, most of the improvements are being handled. With the new improvements that were introduced in MySQL 5.7 and with the testing that we have done to this point, we are looking at updating our web development environment to make better use of the new features.
With the push from MySQL to implement database engines which can provide the same functionality as PostgreSQL and MongoDB, we are looking at application development that leverages this functionality on our current MySQL production database. Seeing that MySQL can provide noSQL document storage the same way MongoDB can and still have a SQL data source next to it creates the possibility of using the best features of both to achieve the desired application result without changing our current infrastructure drastically.
It must be noted that we are still in the process of experimentation to find the best ways of utilizing these data technologies in our current enterprise applications, but not having to move to other database providers to have the functionality means we can experiment without the need to change our base processes. So when I say that the improvements are being handled the MySQL development team have given us access to functionality which we started to look at about two years ago.
The dynamic scalability, clustering, dynamic replicas safeguard against failures, ease of setup and use all need to be improved.
- MySQL was originally meant for a single server; now with the 5.7 version, they have introduced the multi-master model but it is on the user to ensure that there is no conflict of data. Also, to add/remove a server from the cluster requires downtime and MySQL won't scale load on its own as it has scaled up/down (the load distribution has to be done on a separate layer).
- MySQL does not understand the clustered model, it is not aware of others in the cluster and won't act as a player in the cluster.
- Data corruption or two different updates to the same record are not sorted in the replicas and needs manual intervention.
- The cluster setup is complex and so is its maintenance.
- It is not equipped to take advantage of the Cloud (AWS, Azure etc) and their pricing models (go as you use).
SA
reviewer1544529
Project Manager at a computer software company with 1,001-5,000 employees
The solution could be more secure.
RM
reviewer1531995
Senior Director IP led Services (PES) at a computer software company with 1,001-5,000 employees
I'd like to see some additional JSON query support in the solution.
VR
reviewer1489614
SVP Technology and Head of India at a financial services firm with 201-500 employees
The technical support should be more knowledgeable and available worldwide.
View full review »GO
reviewer1301145
CEO at a computer software company with 11-50 employees
We would like to see more security.
View full review »Only one of the engines, InnoDB, supports ACID transaction control. The best performance engine, MyISAM, has no transactional control support.
It would make a lot of sense to include one engine that offers both very good overall performance and transactional control support.
All versions of MySQL, including the Community Server version include in its design as a Pluggable Storage Engine Architecture.
This architecture allows for the support of multiple options of Storage Engines, so, a software architect can design a sofware solution with MySQL based on a specific Storage Engine that is capable to cater to a particular type of storage use case requirements, like for instance, web applications with heavy read workloads and moderate write workloads, or intranet desktop applications with heavy write workloads.
Depending on the version of Community Server installed is the list of available Storage Engines: All it takes is the execution of the command SHOW ENGINES to retrieve the list of installed Storage Engine plugins.
When you create any given table in MySQL, you have the option to select what Storage Engine (among the engines available) will be applied to said table. If this option is no explicitly mentioned at the end of the "CREATE TABLE" command, the current default storage engine will be assumed.
For web apps with intensive read workloads and moderate write workloads, the engine that offers a good overall performance is the MyISAM engine, but this does not support ACID transaction control, and it uses a table-level locking mechanism (thus, from a performance standpoint, this is not proper for apps with heavy write workloads).
The InnoDB engine uses a record-level locking mechanism, so, it is proper for apps with heavy write workloads. It also supports Isolation Levels, which is important for applications that have many clients doing read and write operations concurrently.
The other storage engines offer support for very specific use cases, like for instance, flat file tables (CSV engine) or memory-only tables (Memory engine).
Getting back to the InnoDB engine, it offers features that are similar to the database engine in SQL Server, and according to some of benchmarks that we have run, SQL Server Express provides overall better performance than MySQL Community Server with InnoDB tables.
My "Room for Improvement" comment is that it would be great if in the future Oracle were to provide with the Community Server edition a version of InnoDB with better overall performance, while still requiring a small hardware footprint.
View full review »None that I can name. At the moment I worked with MySQL, there was nothing I couldn't do with the product.
View full review »
It is a community driven project, which means that support is sometimes scarce and hard to find. Also, it really doesn't have an IDE per-se, like MSSQL does.
View full review »
AV
Alvaro Valdes
Information Systems Computer System Controller at a insurance company with 11-50 employees
There are some issues with compatibility with Java environments that need to be improved. When Oracle bought this solution there were some driver changes that caused some issues with operations.
View full review »VR
reviewer1519272
Full Stack Developer at a tech services company with 10,001+ employees
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.
View full review »- I think a better front end would be a better solution (web application front end, similar to what Red Hat is doing to Fedora).
- Another nice solution for MySQL clustering would be the use of Webmin.
- Also, security measures could always be improved, and the clustering process could be enhanced as well. I recommend using UFW, iptables, and firewalld.
I feel that some tools which make it easier to create queries or make it easier for other functions would be really interesting to see.
View full review »In MySQL, you can only have one master. The master's scalability was always a problem.
The cost towards the locking and the patent. What happens, we will be running the MySQL network, and what happens sometimes in some cases, the master go down. Thus, we have to theoretically play the whole thing. The chances are quite high that you are going to lose some important data.
If we can make them implement the system so we are not losing our data, then magically you could say the system would be better.
View full review »The work bench has some bugs that are mostly GUI related.
View full review »DY
reviewer1399998
Deputy Manager at a university with 1,001-5,000 employees
The documentation is pretty weak and should be improved.
The GUI for PHP MySQL Admin can be improved because it is not very flexible and sometimes difficult to use.
View full review »MySQL needs improvements on its diagnostic features.
View full review »Hardware scalability and parallel treatment can and will be improved in the next few years.
View full review »ITIL implementation:
GLPI has a poor ITIL implementation in the sense that not all ITIL processes are implemented, e.g., no Service Catalog is present.
- Limited storage capacity
- Support for foreign keys
- Stored procedures
- The biggest disadvantage of MySQL is MyISAM system, which doesn't support well transactions (lack of efficiency)
Few cons in MySQL are
1) Increased complexity in InnoDB
2) Slower performance when using InnoDB as compared to MyISAM for using simple queries
3) Only identical MyISAM tables can be merged.
4) No active directory integration as in SQL server
5) It does not support check constraints
View full review »
JI
reviewer1707912
System Analyst and Team Lead at a tech services company with 11-50 employees
The licensing of the solution is on the expensive side.
RP
reviewer1362969
IT Specialist at a government with 1,001-5,000 employees
The solution could improve by having better performance and security.
View full review »AA
Antonio Arcucci
CEO at a computer software company with 1-10 employees
Improvement areas are Security and ORM, for example:
It may be interesting to check the user-level access rights at the row level and a robust support to JSON model object (like NoSQL database).
View full review »Multi-master replication could be a bit more reliable.
View full review »Catching up with proprietary technologies like Oracle and PostgreSQL is the challenge right now.
View full review »There should be more tools to manage the on-premises version and more automation features.
View full review »MU
Manzeel Uprety
Co-Founder at Mero Reading Room
The only service which could be improved is its usability. The entire user experience needs to be revamped to meet the 2018 design standards.
View full review »I'd like to see Oracle provide more certification for it.
View full review »
Back in the days, our only gripe about MySQL was that it was a purely command-line based system. We don't really see it as disadvantage though, as it allowed it to be fast and very reliable. This has been addressed through the years with graphical management systems for MySQL. MySQL is a highly recommended product. I give it five stars as it really gets the job done without much of a hassle. Being available for the many platforms also makes it a very compelling choice for mixed-OS environments, as data migration can just be as easy as backing-up and restoring on another server even on different operating systems.
View full review »
KB
teamlead968247
Team Leader Presales at a comms service provider with 51-200 employees
Scalability could be improved.
View full review »Not at the moment in my current work environment.
View full review »Security in the data files needs manipulation.
Software and web development.
AS
Azis Susetio
EUC Techical Operation at a tech services company with 10,001+ employees
MySQL doesn't have the auto-clustering and database clustering features that other competitors provide. They can include these features.
View full review »Scaling.
View full review »Scalability: In large databases, they become slow.
View full review »
DELETE and UPDATE statements that use a LIMIT clause without an ORDER BY are non deterministic.
Statements using any of the following functions cannot be replicated properly using statement-based replication: LOADFILE (), USER ().
View full review »
DM
reviewer1435281
IT at a construction company with 201-500 employees
The manuals or documentation could be better.
View full review »When working with a cluster wide, I have to use the MySQL cluster version.
- Real-time
- Event driven results
- Geolocation data
- Non-text storage
It should provide detailed debugging with transaction IDs at the application level to understand deadlocks, especially under bursty workloads.
It should also provide partitioned tables and a clustered index, like Oracle, to take advantage of inherent parallelisms in the application domain.
View full review »I think it is where it needs to be. MySql PaaS. But, you do need to have experience with SQL to use it.
View full review »I am not up to date on this issue.
View full review »MyISAM tables could be more reliable.
View full review »CL
reviewer1410678
Data Analyst at a tech company with 51-200 employees
It is not as powerful as SQL Server. It can be more powerful.
It is not scalable and has certain limitations, which is not the case with SQL Server.
View full review »How to scale out with shard clusters.
The way how to handle replications needs to be improved, as we noticed that there are some performance drop of (using only one core for example)
• MySQL has a limited storage capacity. It doesn’t support large databases.
• Database transactions are not handled efficiently.
• Unlike Oracle, MySQL doesn't have Tablespace, Role management, snapshots, synonym and packages.
• For transferring data, MySQL doesn’t support other languages being executed from within the system, and neither does it supports XML.
• Compared to Oracle, MySQL database does not support any feature like Audit Vault on its server
• There is a limited scope and earning available for database administrator of MySQL.
View full review »
Configuration templates and reliability both need work.
View full review »CM
reviewer1514799
Project Business Analyst RPA at a consultancy with 11-50 employees
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.
View full review »Maybe the way to build clusters needs to be improved. They could also improve the installation process.
View full review »The online backup needs to improve.
View full review »
1) Does not provide good development and debugging tools, so it’s cumbersome to write large SQL statements.2) MySQL uses temporary tables to execute queries, so it consumes more space.3) MySQL is missing some RDBMS features like stored procedures, foreign keys, transaction, rollback, and subselect. And it also does't support triggers.It is widely used in web applications, and several software stacks includes MySQL as a Data Base Management System like (WAMP, XAMPP) considering its flexibility and simplicity.
View full review »
From the perspective of the company, you can count on reliable Microsoft SQL or Oracle. If MySQL gets solid, it will be a good solution.
View full review »
• It doesn't support stored procedures.
• You probably wouldn't use it for heavy-duty installation.
• There is no active directory for integration with Microsoft SQL Server or other data bases.
View full review »
Buyer's Guide
MySQL
March 2024
Learn what your peers think about MySQL. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
767,995 professionals have used our research since 2012.