MySQL Reviews

We are using MySQL for backend operations since we are a software backend developer. We are using this tool in our backend application for acquiring the data.

We mainly use MySQL for our Relational Database Management System(RDBMS). We are maintaining our customer data in a defined way. We have to create various schema levels. We are presenting the customer data, such as name, mobile number, what was purchased, and what they like or dislike. Once we create the schema, a set of data, we need to maintain the unique constraints.

For example, for customers, we'll assign a unique ID to each record, that will be a primary key. All these SQL constraints we'll use and there should no variance or replication of data isolated. When we perform any update operations, it should not affect any of the data isolated. 

We need to take care of many things, such as consistency, isolation, and variability for constructing any database. There are a few more concepts as well, such as normalization and PL/SQL. For example, if I want to run a job at a particular time, the product will use PL/SQL. We are like implementing our coding skills to databases.

Our operations are on-premise. However, we are in the process of moving everything to the cloud.

We have many repositories in one table that we are completing for customers' data that are store product data. There are various pieces of data and data should be in the same format. For this purpose, we are using RDBMS. The data in the repository should be able to be accessed in one place which is Oracle SQL Developer. MySQL can store data for a longer duration as compared to other data solutions, such as MariaDB, which can only store data for one day. MySQL can store data for a longer period of time, and we can have primary and secondary data as well for backup purposes.

MySQL is easy to use, has fast performance, and it is comfortable for end-user to use. The schema level and structure we are using are very simple and easy to understand. Additionally, packaging tool development is straightforward and the data is presented in a way that is very simple to understand.

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.

I have been using MySQL for approximately four years.

I have found the development tools to be highly stable in MySQL.

The scalability of MySQL is very good. There are no barriers to it. It can be used and accommodated in any particular language. We can use it with Java and Python.

We have almost everyone in my organization using the solution. We have developers and support teams all using it. If my organization has 1,000 people, almost 900 people out of them were using the service.

I have evaluated MariaDB.

We use a solution called Jenkins to help us with all the pipelines. The pipelines are all created and configured in the Jenkins. We are in a distributed server architecture and the full process can take approximately 20 minutes for one server.

If we have a large amount of data we have to take care of it. If this particular data is not used over the years, we have to make maintenance decisions on it after we use it. The developer administrator and the team will be responsible.

We are using the licensed version of MySQL.

I would advise others that this is a useful tool.

I rate MySQL an eight out of ten.

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. 

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.

The most valuable feature of MySQL is auto-scaling.

The GUI could improve to make MySQL better.

I have been using MySQL for approximately four years.

The stability of MySQL is good.

MySQL can scale well.

I have used the support and level three support is great.

The initial setup of MySQL was straightforward.

We have not seen a return on investment.

The price of the solution is good because we have a good partner.

The solution is good at scaling.

I rate MySQL a ten 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.

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 MySQL for customer management authentication in our company.

The use of MySQL is really dictated by the software we use. So we have put software that dictates the use of MySQL and MongoDB. We think we've found the goal of the company related to strengthening its business systems.

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.

I have been using MySQL for three years. It's based on the call systems or based on the console.

I rate the solution's stability a ten out of ten since it has been running flawlessly.

It works well. So, I rate its scalability a ten out of ten. Our company is managing hundreds to thousands of clients, but we use MySQL for different projects. So, around 50 users work on it.

In terms of increasing the solution's usage, I think we've done enough, like, stabilizing MySQL.

Our company has contacted the technical support of MySQL. It was very easy to get connected to them. However, it cost us a fortune. For SMBs in South Africa, a thousand or ten thousand dollars an hour is a lot of money. It was expensive, but it was worth it.

We have previously used a solution for location and mapping-related stuff. Our choice to move to MySQL was dictated by software. So, we use different programs for applications.

The initial setup is straightforward. The deployment process takes a few seconds.

We had to seek the help of some consultants to implement the product since there was some difficult stuff. But that was long ago. Nowadays, we avoid seeking help from consultants since it has become pretty simple. So, better experienced and well-trained people would do it for us. It's not a problem.

I believe we have a few cluster solutions. I think that MySQL is a premium product. But I don't manage that part.

The solution's documentation and support are awesome. Also, its speed has increased in the last few years. So, we have never had any issues with it. If there were any errors, then they were human errors.

Today with many other options, we stick with MySQL and recommend it to others. There are so many other things that are more suitable for different purposes, and I will have to do research to know more about them. MySQL has been around for a decade, so something cannot go wrong. Its big support communities make it easy to resolve problems since there is always somebody who can help.

I rate the solution a ten out of ten.

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

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

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

I have used this product for two years.

There was no issue with deployment

There were no issues with stability

There was no issue with scalability

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

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

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

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

I did the installation.

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