MySQL Reviews

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.

More than five years.

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.

• Excellent performance, mainly due to the format of its default table, MyISAM - low disk space, CPU, and memory
• Flexibility offering multiple variations such as Berkely DB , InnoDB, Heap and MyISAM
• Reliability. Although the system runs on Windows without flaws, it tends to perform better on Linux and other UNIX-like Systems.
• Availability
• Open-Source System, open storage database engine
• Used by many websites (e.g. LinkedIn, Facebook, Verizon, and PayPal)
• It's inexpensive when compared to other common databases like Microsoft SQL Server.
• As a developer myself, I enjoy using it at no cost as long as the associated projects are also open-source.

• Limited storage capacity
• Support for foreign keys
• Stored procedures
• The biggest disadvantage of MySQL is MyISAM system, which doesn't support well transactions (lack of efficiency)

Personally, I've been using it for over 10 years, and professionally for three to four years.

I had no problems deploying it.

With each release of MySQL Server was useful for any little problems that users detected, so I would say it's quite stable.

It was straightforward, thanks to the workbench that pulls together nearly every MySQL task, and puts them into one easy and friendly GUI.

Because MySQL is an open-source , the system is under GNU Licence. The system isn't always free, but it's more affordable. If you intend to sell your software as a proprietary product, you would need to purchase a commercial license, which is quite inexpensive when compared with a Microsoft SQL license.

From my perspective, MySQL is a product that allows you to be efficient, but the decision goes down to the situation and what you're looking to accomplish.

The best features in MySQL, making it one of the most used databases globally, are- 1) Multi-threaded architecture for multiple CPU utilization and kernel threading 2) Use of triggers and crash recovery techniques 3) Indexed Conditional Pushdown 4) Integration with LAMP/WAMP 5) Easy setup with Memcached for increasing performance and scalability

Few cons in MySQL are 1) Increased complexity in InnoDB 2) Slower performance when using InnoDB as compared to MyISAM for using simple queries 3) Only identical MyISAM tables can be merged. 4) No active directory integration as in SQL server 5) It does not support check constraints

MySQL is indeed the world's most popular open source database. It has been designed on the hyper threading infrastructure and supports multi-threaded architecture for using multiple CPU's. It works on index compression with B-Tree disk tables popularly known as MyISAM. Its efficiency depends on the implementation of SQL functions with optimization of library classes.