MySQL Reviews

It's been used as a primary relational database for most applications. It's scalable and could easily be maintained and could be migrated to any Cloud-based Database as a Service solutions which are compatible with MySQL.e.g. AWS RDS MySQL, AWS RDS Aurora, Google SQL. 

It has improved scalability, easy-maintenance. It is open-source and is easy to use. 

MySQL is open-source. There are a lot of open-source communities trying to come up with their own patches, and to come up with their own features, which help MySQL develop faster than traditional databases like Oracle, which is closed source.

The solution is also compatible with a lot of other databases, like Percona, and it's compatible with MariaDB. It's also compatible with a lot of other shared database solutions.

Since MySQL is mostly used as a relational database in a lot of organizations, a lot of other solutions are being merged with MySQL and it's a rather easy process.

Unlike a lot of closed source services, the new features are solely based on customer feedback. The customer feedback of open source is way larger than the closed source application.

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. 

I've been working on Relational Database MySQL throughout my career, i.e. for 14 years. This relational database MySQL is evolved from its MyISAM only engine to InnoDB and is now compatible with other database engines too. e.g. NDB, Galera. 

MySQL is reliable. If you are talking about it in terms of relational databases, MySQL is pretty stable. If you want to go ahead with a quite secure database like any PCI database or a customer-related database or even financial data, it's still feasible to migrate to MySQL. 

There are a lot of features provided by Oracle MySQL, Percona, and MariaDB. They all have their own replication cluster. Percona has XtraDB, MariaDB has GaleraDB, Oracle MySQL has its own cluster as well. MySQL replication is common in all three MySQL flavors. MySQL replication is an excellent read-scalable feature, which has also evolved a lot from its earliest versions to the latest 8.0 version.

The NDB cluster, which has been supported and developed by Oracle, and is based on MySQL, is different than all of the other MySQL replication cluster solutions. It's both read and write scalable. All other cluster features work well for read scaling. NDB cluster is the only cluster feature recorded by Oracle MySQL, which is write scalable as well as re-scalable.

The solution seems to have plenty of technical support due to the fact that there are three companies who are product owners, and therefore there are three companies who are supporting MySQL. They are: Oracle, Percona, and MariaDB. They're doing pretty well. 

There are a lot of companies also that support their customers. This is the good thing about any software which is open-source. A lot of open source communities come up with their own features and they try to patch up with the original source. 

The initial setup has evolved a lot. It's pretty straight forward whether you're using Mac, Windows, Linux, etc. You can set it up on almost every operating system. 

It's supported by the open-source community, and they have plenty of documentation online that users can reference for assistance. If you are working in almost any operating system and you have any questions related to the installation, you'll find the documentation you need.

I am not sure, what the licensing costs are for the solution. From my experience, there is no straightforward cost. You can get that cost from the Oracle website about the Oracle MySQL licensing costs, however, it's not a straightforward price quote for everyone.

If you are an existing customer, you can negotiate and you can get a better quote. The pricing on the website may be for new customers. That said, you can still negotiate. The same is true for Percona and MariaDB as well. 

We are using MySQL 5.6, 5.7, and MySQL 8.0. 

In terms of advice, I'd say when implementing MySQL, if a company has been using any previous relational database, like Oracle, Microsoft SQL or DB2, the easiest way to migrate from any database is from Oracle to MySQL. There'll be some challenges from Microsoft SQL, as well as from DB2 to MySQL. Any existing application which is working with the Oracle database as a backend database, DB2 database as a backend database, or Microsoft as the backend database, should still work fine with MySQL, with minimal code changes. 

MySQL is a product supported by a lot of applications and a lot of organizations. Almost every client and every API would be able to support MySQL. There would still need to be a lot of testing, however, I feel almost all of the applications which need a relational database for their database solution, could leverage out of MySQL. 

Our primary use case for MySQL is for running applications on our Linux boxes. We have very few applications that run online, but we use MySQL on those boxes, primarily for our email system. We haven't considered working on cloud, so all our solutions are on-premises. 

One of the most valuable features is MySQL's ability to run our email system. We use a system called Colab. 

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. 

I have been using MySQL for a few years. 

This product is stable. I'm very satisfied with the performance. 

Since MySQL is running our email system, there are around 200 users. It's installed on one of the servers and the admins are the ones who interact with the system itself if the need arises. 

I have never contacted Oracle's technical support. If we have any issues, we've got some recommended support people here in Zimbabwe that we contact. 

I didn't use any other solution before implementing MySQL. We also use MariaDB, but not on a very big scale.

The installation was a very straightforward process. It took about a day and we did it ourselves. 

We implemented through an in-house team. One person, the admin, can handle it. 

We are using the free version of MySQL. We prefer paying for a yearly license. 

I rate this solution an eight out of ten. I would recommend this solution to others and I'm very satisfied with its performance. 

The solution is primarily used for mobile applications and IoT-based services. It's a good choice for development. 

The solution is very stable.

The scalability has been great.

The deployment process is pretty fast.

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.

I've been using the solution for a couple of years.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution is scalable. If a company needs to expand it, it can do so. It's easy.

We have 500 users on the solution at this time. We are likely to increase usage in the future. 

We don't really have access to technical support. Our engineers have to spend time looking for answers on Google. 

Previously, we only used Oracle databases, which were expensive. We've moved away to other DBs and have begun to use MySQL.

The installation process didn't take very long. It took about three or four hours.

We have five people, who are engineers, that can handle setup and maintenance tasks. 

I handled the implementation myself. I did not need the assistance of any integrators or consultants. 

You do need a license in order to use MySQL.

The solution can be deployed both on the cloud and on-premises. 

I'd rate the solution at an eight out of ten.

I would recommend the solution to other users and organizations. 

We're on a software development team. We develop applications.

We're currently running version 5.7 of MySQL, and we are going to be upgrading to version 8 this year.

MySQL server currently is in a co-location center. We've got a hosting provider that takes care of that for us. We are looking at moving it into AWS, but that won't happen this year. We do have a smaller MySQL RDS instance in AWS right now, but it is pretty minimal. 

It is free, which is probably its most valuable feature. It is a pretty full-featured relational database. It really does everything we need it to do. 

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.

I have been using MySQL for seven years in my current company, and I have probably used it for another two or three years in a previous company.

It is very stable.

I haven't dealt with them.

We're using the open-source version right now, which is free. I do see some value in some of the more enterprise functions. We're using the open-source version right now, and I was interested in the MySQL Enterprise version really for the tools that they provide, but we decided not to make the purchase.

There are certain things that it doesn't do as well as SQL Server. There are certain things that you can do to swamp the server, such as it is just not very responsive to more complicated joins and things like that. Unfortunately, you have to try to learn what those things are, but there are certain things like correlated sub-queries and more complicated approaches that it doesn't support, and you can hang the server in doing that. So, even though it has standardized the SQL queries and other things, there are some things that it doesn't perform particularly well, such as more complicated joined scenarios. We join several tables at a time, but we tend to do that on well-known indices, primary keys, and things like that, but if you're doing something more sophisticated than that, it becomes more challenging. These things that I've mentioned are written up by people, and once you learn those things, you develop techniques to work around them. You take different approaches to solve the problem for those things. You have to do that anyway as a developer. You don't just write code and throw it out there on a production server. You certainly need a totally separate test environment and all that.

I would rate MySQL an eight out of 10.

We developed a network monitoring software and used MySQL as a backend database.

We utilized the two most common and popular MySQL database engines, MyISAM and InnoDB.

We store collected monitoring data and configuration data on MySQL. Also, our network monitoring solution reporting module is based on the MySQL MyISAM database engine.

We use both Windows and Linux versions of MySQL, and we utilize the backup and recovery features.

To summarize, our primary use case is the embedded DB component for our network management software.

MySQL is a popular database platform for businesses because it is extremely easy to use. It is commonly used in combination with PHP and Java. For instance, someone with little to no knowledge of MySQL can easily establish a database connection and start programming immediately.

So MySQL improved our developing process speed. MySQL is a very popular and well-known database solution, so it is easy to find a MySQL developer.

MySQL performance also improved our NMS solution performance.

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses.

MySQL advantages and valuable points include:

• MySQL is a very powerful program in its own right. It handles a large subset of the functionality of the most expensive and powerful database packages.
• MySQL uses a standard form of the well-known SQL data language.
• MySQL works on many operating systems and with many languages including PHP, PERL, C, C++, Java, etc.
• MySQL works very quickly and works well, even with large datasets.
• MySQL is very friendly to PHP and Java at the same time. Both PHP and Java are our development languages.

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.

We have been using MySQL for more than ten years.

Previously, we used MSSQL and switched to MySQL because of performance issues.

After installation, the maintanence is easy for an end-user.

MySQL is released under an open-source license, so you have nothing to pay to use it.

I used it for a small customer database company in England with 20 employees. They didn't have that much data, and we needed something easy to install and easy to run. This was my use case for it.

My main reason for using MySQL for this small customer database company and for some kinds of scientific projects was that I had to do the installation myself. I didn't have a database administration team behind me. Therefore, I was looking for something very easy to handle. MySQL is easy to install, connect, and do all such things.

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.

I have been using this solution for two or three years.

I used it for a small customer database company in England with 20 employees. There were only two people using it. It was really a small solution. For this purpose, it was perfect, but I'm not sure how it scales. It was just not an issue in this case because we had very little data. 

Their technical support is fine.

It is easy to install. It takes just a few hours.

I will probably keep on using this solution. If you have a limited amount of data you want to store in the database, and you don't want to spend a lot of time on administration, it is certainly fine. 

I would rate MySQL a ten out of ten. It was perfect for our use case. 

We are primarily using it as a database for our products. For internally built systems, we have MySQL. We use it internally.

It's our database due to the fact that it's cheaper and is actually free to use.

The product is very easy to use, yes.

It's quite stable.

The solution is very compatible with many versions of Linux. Most of Linux is free, so it's easy to implement with MySQL. Whether it's Ubuntu, CentOS, or different types of Linux, it's the same across other operating systems, and therefore it's very easy to use and compatible with any demand that comes from developers. At the end of the day, MySQL is compatible with most of the platforms.

The solution has been very easy to scale so far.

The installation process is very easy.

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.

I've been using the solution for more than five years at this point. It may be as much as seven years or so.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable in terms of performance.

The solution is very scalable. If you want to install it in the machine and scale that machine, you can do so. Or you add more machine nodes whereby you are actually clustering items and you're clustering your database within one site. The solution will actually extend these needs to another site for replication, DR replication.

We have about 20 people using the solution currently.

We do plan to continue to use the solution in the future.

All of our support is internal. We haven't subscribed to outside technical support.

That said, we haven't had any issues with the solution that would require support assistance either.

The initial setup is not complex at all. It is very easy to install as most of the Linux comes embedded so that even if you're under a different administrator, you should be able to just click and install.

Installation doesn't take more than 10 minutes for me. It might take up to 30 minutes or an hour for someone who is new. However, for someone who is used to MySQL, doesn't take more than 10 minutes to set up.

For deployment and maintenance, basically, we would need about three engineers. The one that actually does the hardware infrastructure, the one that does the operating system, and then the one that actually does the MySQL, which is the database administrator.

I handled the implementation myself. I did not need the assistance of integrators or consultants. 

The solution is absolutely free to use. It's one of the reasons we've chosen it.

We do evaluate other solutions. We also use other products, such as Oracle's SQL server.

When a trace comes for MySQL, we will check mostly the cost of installation and the cost for maintaining everything. We are choosing MySQL over the others that are actually licensed solutions mostly due to the fact that MySQL is free.

We are just customers and end-users. We don't have a business relationship with MySQL.

I'd recommend the solution to other organizations.

I would rate it at a seven out of ten overall. 

My daily tasks are related to data mining and TBICO Spotfire is one of the products that I use. We are a small group of geologists operating in a niche area who are analyzing geochemical data. Our backend database is MySQL and we use products such as Power BI, Tableau, and Spotfire to display data for the geochemists.

I perform data-related tasks such as data manipulation and creating views, then updating the database afterward, all using SQL queries. As part of this, I'm making entries as needed or corrections to data that has already been processed.

Essentially, I'm doing data mining with SQL queries, although I wouldn't call what I am doing Data Mining exactly, because I already know the data model. I know the geochemistry data in my head, so I already know what I'm looking for when I write an SQL query. We're not doing machine learning or AI at this point, although it may come in the future.

Every now and then, we create dashboards for the geochemists, which cover their needs from the data.

The most valuable component for me is SQL Developer. It is pretty simple to use and I don't have anything really bad to say about it. It supports multiple window displays and all of the connections are available. A lot of people use Toad for this type of work, but I have not myself.

The functionality that I use most often is querying the data model.

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.

I have been working with MySQL for approximately nine years.

This application is pretty easy to scale.

Within my department, which is technical data management, approximately 75% of the people use MySQL.

I have never had to deal with technical support from Oracle directly. We just raise tickets that go up and show operations, and in turn, they are the ones that deal with Oracle.

I have used several versions of Oracle MySQL including 10, 11, and 12, and I don't really see any difference between them.

MySQL comes pre-installed with our new PCs, so I have never been involved with the initial setup.

On the operations side, based on what I have seen in terms of people putting in tickets for issues, it seems that we have three people who support and maintain MySQL at different levels. I feel that having this number of resources assigned to maintaining a database is wasteful.

I think that a single person can be in charge of maintaining multiple databases.

As a data analyst, I am not in operations and don't have a say in which products we use.

My advice for anybody who is implementing MySQL is to ask around because there are many different ways that you can create a database now. Relational databases are no longer the best way to organize your data. It really depends on what it is that you're doing. For example, you may not need a relational database, but instead just a file structure. So, look at all of your options and speak with the experts to see what kind of database is needed before assuming that you need an RDBMS.

I would rate this solution an eight out of ten.

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.

It is an ideal database to use online learning environments and SMEs. It works well with  Moodle, the open-source learning solution, and is the defacto standard for that product as Moodle is written in PHP which generally goes hand-in-hand with MySQL. As it is an open-source and free solution it is an economical method of storing important companies or small business data. At the same time, it offers a rich set of functions comparable to other large-scale enterprise solutions such as SQL Server and Oracle. 

MySQL is easy to configure, use, and implement. It is free, and cost-effective, with a powerful plethora of tools. It has improved my organization for my clients using Moodle and MySQL databases, as problems are usually easier to fix quickly, and the database resources can be optimized, easily. Even though it is not as sophisticated as SQL Server and Oracle solutions, it is the database of choice for most Moodle implementations. It has a history of reliability, which is always useful in a business environment.

The Cross-platform support for MySQL is great, as you don't need to worry about which platform or operating system you need to install the platform. This allows for interoperability.

Like other databases, it has a rich set of functions, such as stored procedures and its own procedural language, which is akin to Oracle SQL. It also has trigger and cursor commands you would expect with a good database language.

Views are updateable, which is useful when you need to amend a specific view of data for different circumstances.

It has it's own Data Definition Language (DDL), and provides an Information Schema, to view what is "under the bonnet" of your database.

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.

I have been using MySQL for about 10 years.

MySQL has a reputation for stability, and that is one of the reasons it is so popular. Because it is easily available, just works, and can be integrated reasonably easily into other software, it is often the default platform of choice. 

It has been around for years, and chances are it will be around for the next 10 years or so, as new versions continue to evolve.

MySQL is scalable for SMEs and works on a number of different operating systems.

I have not had many issues with MySQL in the past, so I rarely use the support service.

I have used various databases in the past, but for my current business needs, MySQL is ideal.

It was a simple setup, as it was included in the Moodle installation process for implementing learning sites.

ROI is not applicable, as MySQL is open source and is free, so you could say it is only the investment of implementing the database in your environment.

Pricing depends on the size of your business. For an individual to SME sized business the MySQL solution should be adequate for your needs. Setup costs are minimal.

Yes, but for Moodle Learning sites, SQL Server is more complex, and is not multi-platform, Oracle is not recommended for Moodle, but the nearest to MySQL is ProstgreSQL. MySQL is reliable and easy to use. 

You do need to have technical knowledge of databases in general, but MySQL is not too difficult to learn if used alongside PHPMyAdmin, but there are other tools you could consider, such as MySQL Workbench.