MySQL Reviews

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.

The multiple engine replication is the most valuable feature. This neuralgic process for billing needs high availability and that is where we need this robust, but simple solution. If one server fails, we switch to the other transparently.

It facilitated fast processing of the millions of records for billing of the the call detail records in the Telecom company. The company needed to recover calls, in addition to immediately detecting frauds in the telephone calls so as to block the line and generate large losses. With the help of stored procedures, functions and triggers, we created an engine to recover most of the calls with a single transaction. Thanks to MySQL.

There were no stability issues.

There were no scalability issues.

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

We were using PostgreSQL. The reason why we switched to this solution was that of the easy administration.

The setup was easy.

It is open source and AWS provides a managed solution.

Amazon has come up with Aurora, a MySQL hybrid that has helped us get up to speed without actually thinking about MySQL underlying optimizations.

Catching up with proprietary technologies like Oracle and PostgreSQL is the challenge right now.

We have used this solution for over four years.

There have been no stability issues yet.

We code for horizontal scaling and hence the only thing that becomes important is the number of connections. The data can be easily replicated in real time on Amazon replicas themselves. We have a dynamic solution to read data from replicas and not from a master instance. That is how we scale.

I would give technical support a rating of 10/10.

We did not use a different solution before.

The initial setup was straightforward.

Keeping something similar to AWS, and as easy as Amazon, will be the best thing for any small business like mine.

I did evaluate other solutions, but MySQL stood out because of its ease of use. Perhaps my prior experience has made me be biased towards MySQL.

Until you have expertise in data migrations and what you are doing with data, MySQL can be really easy and dangerous at the same time. MySQL doesn't give you a warning about data truncation if data types don't fully match. Be really careful on that front.

MySQL 5.6 has a great many new features, including, but certainly not limited to, a number of performance improvements.

However, besides the widely talked-about features such as InnoDB, there's also support for full text search, optimizer, performance schema improvements and GTID.

In order to change the size of InnoDB transaction log files, you have to follow this procedure. Beware that if you don’t follow these instructions step-by-step, your server may not restart or rather it will start with InnoDB storage engine disabled and an error in the logs. So, here’s what you want to do:

1. change (or add) the following variable in my.cnf: innodb_log_file_size = ..
2. stop MySQL server
3. make sure you see a successful shutdown of InnoDB in the MySQL error log
4. move away old log files (at this point I have to double check where they are) by running the following command:
mv /var/lib/mysql/ib_logfile* /tmp/
5. start MySQL server – it should take a bit longer to start because it is going to be creating new transaction log files
6. When you’re positive that MySQL server has started successfully, you can remove the old log files:
rm /tmp/ib_logfile*

We are using this solution for database management.

One of the best features is this solution is easy to use.

The solution could improve by having better performance and security.

I have been using this solution for approximately five years.

The solution is relatively stable.

For what we have been using the solution for it is scalable. However, it could be more scalable.

We have a lot of customers using this solution with more projects coming up. We have overall approximately 500 users using this solution.

The technical support is very good and responsive.

The installation is straightforward. It can easily be installed onto a laptop or any computer.

I did the implementation myself.

There is not a license required for this solution.

I would recommend this solution to others.

I rate MySQL an eight out of ten.

The most valuable feature is the fact that the product is cross-platform, because it reduces server TCO, for my small company. This is very important.

Without MySQL, we used a single centralized database.

With MySQL, we can now have many standalone databases where every developer can perform local tests.

Improvement areas are Security and ORM, for example:

It may be interesting to check the user-level access rights at the row level and a robust support to JSON model object (like NoSQL database).

I've used MySQL for 12 years, since 2005. I chose it after using MS SQL for years. It is more suitable for the projects that we make.

No, never.

Yes, the many index restrictions in case of partitioning the tables.

I do not know yet. I've never used technical support services, only the community

Yes, I first used Microsoft SQL Server, then I went to MySQL because the cost is lower.

The initial setup is straightforward, especially in a Windows environment.

There is no cheap commercial license for standalone applications.

Yes, I have evaluated other database solutions. I have evaluated PostgreSQL and MongoDB.

Simple syntax and simple administration are the most valuable features.

It allows us to maintain very large tables without jumping through the hoops that are required by the commercial products such as Oracle.

Multi-master replication could be a bit more reliable.

Counting the earlier versions, we are using this solution for over ten years.

Compared to the other database solutions, there were no stability issues as such.

Sharding is relatively straightforward.

We run the Community version, so technical support doesn't apply.

We tried Oracle for a while but it was too much of a resource hog.

We looked at Oracle and PostgreSQL.

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