MySQL Reviews

We utilize the DB as a data-repository solution for our front-end applications. The solution gives us the ability to run numerous instances on various geographical cloud servers.

Yes, MySQL has improved numerous processes; it has given us the ability to create applications without absorbing major costs.

• Its ease of use
• It's secure.
• It's fast.
• It has high-end processing.
• It can distribute across clouds.
• It has the ability to run on any operating system.

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

The solution works extremely well. It is easy to install and works on any platform. The price is good because we utilize various versions of the software/DB.

If the user sets up DB up using MySQL Cluster (creates a grid type of design), then we find the solution from a hardware perspective using NVMe, NVMe-oF, 10GE network connections, and 32-100GB of DDR4 memory (dependent upon customer requirements). 

Scalability can be initiated using high-speed connections across IPv6 connections (IPSec AES-256 ESP/AH VPN connections without purchasing VPN concentrators — this can be done at the network layer).

We use various versions, but most of the time this is based on the client's requirements.

After the initial training, the installation worked pretty well. I would suggest setting it up in a lab. This gives the user room to test the installation and configuration process. It is recommended to use PhpMySQLadmin — (https://www.phpmyadmin.net) — after the installation process is completed.

It was implemented in-house. Most of the applications are tested in our cloud and on-premise servers.

60% ROI (There are DLs — direct labor costs and overhead costs, but once it is set up, we image the configuration and deploy our designs in docker).

I would suggest testing MariaDB before jumping in. This will give the user the ability to test the DB before using it. It is very easy to set up. MariaDB is free, and licensing is based on GNU.

N/A.

I would suggest running tests against MySQL, MariaDB, Oracle, PostgreSQL, and MS SQL to determine which one best suits your needs (cost, development, and integration should all play in your decision-making process).

I used it to obtain insight into the entire network and the resources being utilized. The current GUI lets us see the traffic happening east to west and the total bandwidth consumed by it.

• It provides visibility, where something was either broken or in pieces only.
• It creates a unified view of the entire architecture and performance factor, helping to manage the network more easily.
• It has a remote access feature to manage the database from a remote location. This enables in-work collaboration.

I have found the following features valuable:

• NetFlow of the whole system
• Information flow and scaling
• Communication between multiple collaborators and stakeholders
• Its user-friendly features.

The only service which could be improved is its usability. The entire user experience needs to be revamped to meet the 2018 design standards.

The overall service is great. 

I use MySQL for employee service in an OLTP database.

I use MySQL for various purposes. Sometimes I have used MyISAM as a storage engine rather than InnoDB.

When working with a cluster wide, I have to use the MySQL cluster version.

The 5.7 version has very better performance improvement over the previous version.

I'm a tester, an optimization tester. It's basically when the developers have the back-end in SQL. We go and test it out for them and check that the table updated correctly, and we do something on the front-end.

To give you an example, initially we didn't have a database server as such, and we had to make use of some database. Now we use something where we can share the instances of the database which were created virtually, which is a very good feature, which I felt has improved our organization.

The most important features would be querying, the query language where you have the data definition or data modification language, as well. In some cases, we have to create our own tables for testing purposes. In that case, having SQL Server is much easier compared to what's available.

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.

Pretty much since we have our own in-house SQL branch, the administrators are there, so they take care of the stability with the product. As far as I've seen, there really hasn't been much of an issue with stability.

 It's pretty scalable.

I haven't contacted them, so I have no experience with them. We generally have an internal team which would work on it. So our point of contact is an internal team, rather than going to MySQL.

I've used a lot of different solutions. MySQL is one of the top among them. Usability and scalability are some of the reasons we went with MySQL.

It was pretty straightforward. No hassles with the setup. 

Usually the setup is done by the IT admin guys, but it was pretty straightforward. The IT admin guys had to come in and give us the rights to install it.

I'm not sure about pricing, I don't deal with the pricing. It's an organization decision.

There were many options.

No one tool fits the bill for every company. Do a feasibility study, and get to know what is can do before going in and developing.

Web portal database.

• Free usage
• Performance
• Community

Scaling.

There have been some problems with big table operations.

Some problems with big table operations, and a struggle to keep the servers responding in peak situations.

I don't have enough information about it, as I normally look for community support.

Straightforward, and and easy to run.

Can range from free to quite expensive, depending on the environments and requirements, so better to really set goals ahead of setting it up.

SQL Server, Oracle XE, MariaDB.

It is a stable, reliable, and powerful solution that is quite suited for small to medium organizations and/or projects.

We use MySQL and MariaDB for most part of our mission critical applications

This as it is so simple to integrate with web applications, and other well known applications.

Since it has many integrations to web applications, it is very easy to install and deploy open source web applications.

How it uses clustering.

The API's to PHP, ruby, perl, java, python, and many more high level programming languages makes it easy for us to deploy new features fast.

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)

No issues.

Yes, the binary log replication process in a cluster environment has issues processing data as fast as it arrives.

Customer Service:

A 10 out of 10.

Technical Support:

A 10 out of 10.

We have been using many different types of databases, and will most likely use this one for part of our systems, as it is has so much integration.

The initial setup was easy.

We implemented it in-house.

Free.

Be sure to take backups of the solution, as this will check that the blocks are okay.

We decided to use "DB Protection for MySQL" as it has options to perform block level incremental forever, and integrates well with Spectrum Protect.

Yes, we checked MongoDB, PostgreSQL and MariaDB.

It dramatically improved use for several of my customers.

This depends on my customers' use.

SQL and NoSQL use.

When configured correctly, no stability issues.

When configured correctly, no scalability issues.

Very good.

MySQL Support Services by Percona. I switched to Oracle MySQL services because of a better ROI.

There is no obvious answer. It depends.

Depends on the customer's needs. 

MariaDB, MySQL Support Services by Percona.

Stick with the source, stick with Oracle MySQL as the leading vendor for MySQL technology.

Due to the open source licensing model, it has allowed small businesses like ours to adopt enterprise-grade database systems without incurring significant licensing costs.

• Open-source
• Multi-platform
• Lightweight
• Simple to set up, configure and tune
• Support for enterprise-grade features like clustering, master-slave replication, even Sharding (to some extent) which is an advanced feature

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.

For the scale at which my systems are operating, the software is stable. We are at most dealing with less than 10 million rows of data across all tables, and concurrent connections under 200 at our peak loads.

No scalability issues at the scale at which my systems are operating. One thing I did encounter with an earlier version of MySQL 5 – the mysql process will not automatically use available CPU cores on the server, even if it was a dual or quad core CPU. I was troubleshooting a scalability issue when I saw this, it maxed out just a single core and left the other three (in my quad core CPU server) idle. There was a specific condition / trigger that will make the mysql process span the other available cores (I can’t recall now but a quick googling likely will uncover this).

We did not subscribe to professional support from MySQL AB or Oracle. However, the wealth of community support is outstanding. Most of the issues faced could be resolved by knowledge shared by the MySQL community.

I’ve used SQL Server and Oracle for database systems. SQL Server is an excellent solution, in particular the DTS (Data Transformation System) which is not available for MySQL. Switching to MySQL for two reasons: 1) licensing costs 2) the application supports MySQL primarily, and has poor support for SQL Server.

Very easy to set up, relatively easy to configure, tune, and use the conf file, as long as you are comfortable mucking around in Linux conf text files and working from the command line (I am).

You could use the installer which would be the easiest way, but setting up by hand is not too difficult either – instructions can be found online and following them step by step usually works fine.

MySQL Enterprise Support is not cheap, though might still be cheaper than Oracle or SQL Server. They may not have local support depending on where you’re based, but there are many smaller agencies out there that will readily provide support. You’ll need to spend some time looking around.

I’d been using other database systems like Microsoft’s SQL Server and Oracle Database before trying out MySQL. There are forks of MySQL maintained outside of Oracle, like MariaDB and Aurora (by Amazon Web Services). I have not really tried them but I don’t expect very big differences; in fact, for most use cases you may not observe any difference. There would be the few unique features in MariaDB and Aurora that are not present in the original MySQL feature set (I know there are but don’t remember the specifics).

As long as your application supports it well, and you are familiar with the scaling options and its limitations, you can’t go very wrong with MySQL, as it is a very mature product by now. If you are fairly competent with servers and databases you could start off without subscribing to Enterprise Support, and may be able to get by quite well. If things get more complicated, or scalability starts to become a problem, then you may consider paying for help.