MySQL Reviews

MySQL can handle multiple rules of a database within seconds and extract required information for the business case, especially with well-optimized queries.

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.

I have used MySQL for five and a half years in my company, but I have used the tool for around ten years.

MySQL is a stable tool. Stability-wise, I rate the solution a nine out of ten.

MySQL is a scalable tool. Scalability-wise, I rate the solution a nine out of ten. My whole company directly or indirectly uses the tool since we are involved in analytics. My company is an enterprise-sized one.

The solution's technical support is good. I rate the technical support a nine out of ten.

Positive

Since everyone in the industry we are a part of uses MySQL servers, we have also used the same.

The solution's initial setup depends upon the use cases. If you're using it for a simple thing, it's a simple process. But, my problems and statements are quite complex, and I use them to get information, like how the customers perform based on cohort analysis. Also, my use cases are complex, so I have to write complex queries. Overall, the setup process depends upon the scenario.

The installation process is not difficult since it gets pre-installed in all the machines after it is done once. Since the installation process is neither very easy nor difficult, I can rate it somewhere around seven out of ten.

The IT Department handled the deployment process in my current company. Based on my experience deploying the solution in my previous company, its deployment was not difficult. Since everything was already deployed in my current company, we are using the tool as front-end users. When planning to start using the solution, we need to launch SQL server before using it. Also, based on whatever datasets are there, we need to get the permissions for those data sets, after which we are good to go.

MySQL requires maintenance, while the IT department handles the maintenance of SQL server. I am not involved in managing the upgrading part of the tool. Every year, MySQL keeps releasing new versions with new functionalities.

My suggestion to those planning to use the solution is to learn about it and utilize it for their specific scenarios. It is a powerful tool that can perform multiple analyses and reveal hidden insights within multi-million or billion-row datasets that may not be immediately visible to the human eye. The tool also offers many use cases for machine learning. I encourage users to plan and explore the tool to discover its full potential. I rate the overall 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.

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

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

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

I have been using the solution for two years.

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

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

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

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

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

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

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

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

I started to use MySQL at some point when I had some issues that I couldn't get around. I normally use the tool in professional opportunities and when I require support from MySQL.

Cacti is a tool for monitoring devices on a network in graphical terms, for which it uses MySQL or MariaDB. I mostly deploy Cacti with MySQL or MariaDB. Somewhere down the line, I started to have some issues with the permissions in MySQL, including its areas like superuser privileges and similar stuff, which took me a while to figure out. I think the tool is fine for me now.

The most valuable feature of the solution stems from the fact that it helps me to get my work done. I am more interested in getting my work done than any feature it comes with since, as long as it gets my work done, it can actually help me achieve my objectives.

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.

I have been using MySQL since 2014.

It is a very stable solution. I deployed the product six years ago, and it still works fine.

I won't be able to comment on the product's scalability since I haven't deployed it in a cluster environment.

Our company has over a thousand devices, including switches and a couple of other devices, which report to MySQL for management purposes. In general, MySQL is a very robust tool.

Somewhere down the line, I got introduced to MariaDB as well. Nowadays, I use MariaDB rather than MySQL most of the time.

The product's initial setup phase is easy since I use package management software. I mostly take care of the deployment phase with the help of Docker and other tools. If you decide to use the default deployment settings provided by MySQL, then it is a straightforward process to deploy it.

A lot of things have changed since I have deployed the solution. The solution is like a new product nowadays since you just need an application to deploy it presently. The other area where you need to take care of the solution is knowing how to secure it very well so that it becomes less vulnerable and prevents people from taking advantage of the solution.

Mostly, I go to the MySQL website to download the binaries, and I just deploy them on a Windows machine or another system, which is just a straightforward process. The product's installation phase is not much of a problem.

The solution is deployed on an on-premises model.

Earlier in my company, there were three people who used to take care of the deployment of the solution, but presently, I don't know who handles the deployment part.

In the past, the product was free for users, which ensured that users could experience a high return on investment from the use of the solution. I don't know the licensing models attached to the solution currently, but the return on investment is very high if you use it for a very limited amount of time.

MySQL was one of the tools I was introduced to from the very beginning when I was in school. Though I knew about Microsoft SQL Server, the lectures in my school did not introduce me to it since more focus was placed on MySQL. I find MySQL easier to use compared to Microsoft SQL Server.

I recommend the solution to those who plan to use it since it is a very good product that comes to my mind since it is always available. I don't know about the current licensing model of the product because it was an open-source tool earlier. I don't remember myself attempting to check what kind of license MySQL uses presently. In the past, Microsoft SQL Server used to cost a lot of money, which my company couldn't afford at that time.

I rate the overall system an eight out of ten.

I am using MySQL for business data queries.

The most valuable feature of MySQL is its reliability and performance.

The GUI could improve in MySQL.

I have been using MySQL for approximately 12 years.

I rate the stability of MySQL a ten out of ten.

We have approximately 100 people using this solution.

We plan to increase the usage of the solution in the future.

I rate the scalability of MySQL a ten out of ten.

I have not used support from the vendor.

The initial setup of MySQL was easy.

I would recommend this solution to others.

I rate MySQL a ten out of ten.

Below are a few instances where MySQL is utilized. Typically, I have worked on RPA projects. To preserve or update data from the database, I must create a database and data tables, which can be used again in the future or by other processes. Additionally, the data can be shared. I need to store and manage the data for reporting and management purposes.

The tasks I perform, mostly involve sorting, patching, and maintaining data, as well as creating stored procedures.

MySQL's most significant attribute is its capability to create, modify, and maintain databases. This is crucial and advantageous in procedures, such as SOAR. Therefore, all SQL functions are beneficial to any backend developer or developer who requires data storage.

The solution is easy to use and the user interface has worked well in my usage.

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.

I have been using MySQL for approximately five years.

I rate the stability of MySQL an eight out of ten.

We have four to five people using this solution.

I rate the scalability of MySQL an eight out of ten.

I rate the support of MySQL a nine out of ten.

Positive

The initial setup of MySQL is simple. Anyone can do it.

I rate the initial setup of MySQL a nine out of ten.

I can implement the solution by reading the documentation.

We have been looking into another solution called Microsoft Dataverse but it's not accessible to all the processes for our use cases. Additionally, we are evaluating Amazon AWS. We are finding solutions to fit our client's needs.

If an individual is not currently utilizing MySQL, I would advise them to investigate its efficacy in managing and modifying data. Its numerous features can streamline these tasks significantly. For those interested in starting with MySQL, it provides an all-in-one solution for their needs, allowing them to complete numerous tasks with ease. Moreover, I would suggest using available tools to learn how to use MySQL effectively.

I rate MySQL a ten out of ten.

MySQL is user-friendly, making it easy to maintain and modify data. It offers robust security features that enable restricted access based on user permissions. Additionally, it's efficient in loading data and performs faster than many other databases. Users can expect speedy results without encountering significant delays.

We use MySQL for storing data on the web server. It is a competitor of Apache. The solution can also be used for analytics, warehousing, and Big Data.

The tool is open-source and there is no cost involved in its use.

I would like to see some improvements in the solution’s integration aspects.

I have been using MySQL for ten years.

We have optimized and stabilized the solution over a period of eight to six months.

There are around 60 plus users for the tool in our company.

There is a 25 member team involved in the tool’s maintenance and deployment.

I would rate the solution a seven out of ten. The solution’s users have the liberty of custom management. We can implement the solution in Azure, which is Microsoft’s advanced version.

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

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

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

The solution is stable.

The scalability is very good.

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

It is very easy to set up the product.

The support in MySQL is horrible.

It isn't as reliable as an SQL Server.

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

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

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

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

I've also used Postgre and SQL Server.

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

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

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

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

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

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

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

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

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