MySQL Reviews

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. 

I'm using it to create a small database for a project that I'm working on.

The easy access to the data and the ability to sort the data with multiple methods are very valuable features.

It's quite easy to grasp and is really well documented, which are huge plus points.

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.

The stability is really good. I haven't had any issues with it.

The scalability is good.

The initial setup is easy.

I learned to use it in class, and the setup was quite fast because the teacher really helped us to gain access and take the first few steps. The setup took a few hours at most.

I installed it myself.

I use a free version at present.

Plan how the data will be constructed. I had to delete an entire database and start over because I didn't organize it properly. That was a huge block.

I would rate MySQL at eight on a scale from one to ten.

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.

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. 

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.

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 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.

Our main use case for MySQL is for applications and seamless migration to the DR site. And the application in this case is an airport application.

I can meet the RPO in almost real-time. This changes the customer experience. That testing still needs to happen, but that is one of the advantages of MySQL. We have found MySQL to be a very sturdy and strong database. And I have run it in a solution where it's almost real-time, so it runs very efficiently.

MySQL's clustering features are very strong, and you can automate scripting, so that helps. We wrote a Terraform script and ran it. 

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.

I've been doing pre-sales and working with MySQL since 2007.

I would say that MySQL is definitely stable, but its scalability has yet to be tested. I cannot say right now.

We follow an agile strategy, so deployment is done in parallel. In comparison to other databases, I have always found MySQL to be the most efficiently managed. Of course, I don't discount Postgres, but MySQL deployment always has gone smoothly. I've never had an issue during migration, even on the granular level. UID numbers, which we commonly face in Microsoft SQL, have never been a problem with MySQL.

We use the implementation partners for OEM. 

We get the standard packages, but mostly MySQL is freeware. You pay for a license to get the upgrades. We pay for an enterprise license if that is required, but that's not in every case. It depends.

I would rate MySQL nine out of 10.