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

Usually, we use the application for our team to ensure the data is correct.

We majorly use the application now. We can use MySQL to read for our select queries. This helps us to achieve stability.

In MySQL, you can only have one master. The master's scalability was always a problem.

The cost towards the locking and the patent. What happens, we will be running the MySQL network, and what happens sometimes in some cases, the master go down. Thus, we have to theoretically play the whole thing. The chances are quite high that you are going to lose some important data.

If we can make them implement the system so we are not losing our data, then magically you could say the system would be better.

12 years.

No. Not on the MySQL site.

No. Not so far. I didn't see any problems in its scalability.

We are using the community portal technical support, but when we are reaching them, the support is always awesome.

I can give them a 10 out of 10. The best.

Yeah, we used to cheat off MySQL. But in the end, it was somebody else's design. So, we migrated to MySQL. We just migrated from there to here.

It always depends on the use case. The first case was complex where we ended up rewriting all of the test code better than MySQL.

It always depends on the scenarios of the requirement - what all the current scenarios come from. Are these application teams or is that someone who is just getting the product? If someone majorly bunt because they don't want to use a single point of data, we may end up choosing any other solution.

Usually, we would pick a MySQL because of our DBS, because we know how we can boot up or pick on a use case.

You just need to identify why and what are the requirements. Also, you need to listen to news feeds regarding the features you are getting into and the features you will to use from it. Take the time to identify and understand.

• Open Source (It’s free)
• One can easily find help on the web

You can easily build data models both on-premise and on the cloud.

The work bench has some bugs that are mostly GUI related.

I have used this solution for three years.

I did not encounter any issues with stability.

I did not encounter any issues with scalability.

I use the community version. There are ample “Open Source” resources on the Internet.

We used Microsoft SQL and Postgres.

I use MySQL to teach students about databases. They implement projects using this product.

MySQL is lacking some of the features that you find in a commercial product, but it is sufficient for basic functions.

This product is a good teaching tool for students who want to learn about networked databases.

The documentation is pretty weak and should be improved.

The GUI for PHP MySQL Admin can be improved because it is not very flexible and sometimes difficult to use.

I have been using MySQL for more than five years.

I have experience with other full-scale databases, such as PostgreSQL. For use cases where I need full functionality, I would use another product.

I am using the Community Edition, which is available free of charge.

I would rate this solution an eight out of ten.

We use MySQL for enterprise data storage as well as part of the back-end of websites and web applications.

The most valuable feature of MySQL is the informative error outputs of command line interface.

MySQL needs improvements on its diagnostic features.

No issues.

MySQL is not easily scalable on cost effective consumer grade hardware.

I would rate technical support as a 10 out of 10.

Not applicable. No previous solution.

Setup is easy. MySQL of various flavours has community editions to easily test, deploy, and run.

Enterprise editions and support are definitely needed for the heavy users who need direct support. 

No.

One should ensure the availability of proper hardware before any optimization attempt from the software level.

• Vertical scalabity on hardware
• Better hardware usage
• Access performance
• Addressing consistency, scalability and performance issues

Storage and searching quickly on data is no longer an issue facing us using Excel.

Hardware scalability and parallel treatment can and will be improved in the next few years.

For 15 years now.

No, there are only strategies applied by a data scale interval (less than 200 go, less than 1 to, and more than 15 to).

Always due to architecture, data storage, and data requesting irrelevant strategies.

High. There is a lot of documentation, a lot of expertise, and a lot of projects in the world.

We switched to a different solution because of data access issues, speed, and consistency.

Don't use the license version. Open source is enough.

There are a lot of alternative to paid features. It's very hard to find support for this feature.

You will have a lot of work, but you will also avoid a lot of issues due to product immaturity on the database market.

Installation, because in a few seconds, the product was up and running.

It was the first step of the Service Desk.

ITIL implementation:

GLPI has a poor ITIL implementation in the sense that not all ITIL processes are implemented, e.g., no Service Catalog is present.

I've used this solution for two years.

Yes, several unexplained crashes caused dissatisfaction from users.

Yes.

Zero. No support at all. Only forums with no response.

I have not used a solution like this before.

Straightforward.

It was open source and license-free.

Yes, but commercial ones (ManageEngine, EasyVista, Remedyforce).

Not choosing an open source software for this kind of solution. Now, we are looking at ServiceNow Express.