MySQL Reviews

It is free and bundled with cPanel.

Cost effective.

Not at the moment in my current work environment.

Two years, began when I started at my current workplace.

So far, so good due to limited clients at the moment.

So far, so good due to limited clients at the moment.

There is no technical support since it is a CE.

No.

Straightforward.

It's free.

No, because this is bundled with cPanel.

It's good and affordable.

• Relational database (Although it's not 100% compliant with Standard SQL)

• Performance

• Open Source

• Ease of setup and use

• Ease of use with PHP, Python, and Java

Using MySQL helps to keep the costs down. With immense material available on the web, training is easy too.

This is the de facto DB for web development with PHP. If you worked with LAMP environment, this was the M in it (others being Linux, Apache Tomcat and PHP). With open source products, development was a breeze. Overall, this is a boon to small to medium database applications.

The simplicity of the product lets people abuse it. I've seen so many people create tables and add indices in PHP code. Some of these web developers only know some things about the database.

I have used this solution for about eight years.

We did not use a different solution for the applications that use MySQL. I mostly use Oracle for larger, enterprise software.

The initial setup was straightforward. There are a number of Open Source tools, including Toad and MySQL Workbench which helps with configuration and use.

This started as Open Source project under Sun. With Oracle acquiring Sun, MySQL is now owned by Oracle (not the community). Oracle promised to keep it open sourced, but the community is not convinced. So, there is a branch that's called Maria DB that's slowly taking over in some Open Source projects.

That being said, it is still an Open Source product and it is free to use under GPL license. This means you can always, get community support. But, if you want Oracle's support, that is not free.

If you use it in enterprise applications, you may have to purchase commercial license from Oracle. Here is a couple of links that discuss various options:

http://white-paper.b-lay.com/o...

https://www.linkedin.com/pulse...

We evaluated MS Access, SQLite, PostgreSQL, FireBird, and Oracle.

This is a relational database tool for small to medium sized applications. However, this didn't start as a Relational DB, so if you want a truly Relational Database for an Enterprise, similar to Oracle, you may want to look into PostgreSQL, as well. However, MySQL is still a very good database for internet based applications.

Easy:

• Installation
• Customization
• Use

Data is:

• More ordered
• Reliable
• Available in time and form

Scalability: In large databases, they become slow.

12 years.

No.

Yes. In large databases, response times are high.

10 out of 10.

We used this solution, but changed for another because the database was very large.

Configuration was easy and with much support material.

No.

Let them think about the size of the database.

• Compatibility
• Stability
• Maintenance

These are very important points to keep in mind while deploying consumer facing products, it has to work.

It’s been used as the main databases for a lot of the developments we have done.

As for special features it offers, I wouldn’t say there’s a key one, but I do appreciate the stability it has.

• Real-time
• Event driven results
• Geolocation data
• Non-text storage

Over five years now.

No, I’d say this is the best.

It’s not easy to scale horizontally, don’t think it was ever meant for it. Lacks ease of installation and continuous usage.

Not applicable.

No, in fact, I switched away from it in new developments.

It’s very straightforward, really easy to install. Configuration is easy to understand and to change.

Since Oracle bought MySQL, I’ve seen a slow development. I would recommend the community server if you have to have MySQL, but I wouldn’t license or purchase it.

PostgreSQL.

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.

MySQL is strongly recommended for web applications and LAMP architecture systems. The most valuable feature of this product for me is its graphical interface which allows me to do the database administration easily. Another important feature is its reliability, the decent performance, and the fact it is an open source product.

It gives us the opportunity to create backups of our databases easily and loop through them with minimum effort.

I think that the stored procedures and the development tools to write and debug large queries could be improved.

I have used MySQL for about 10 years.

There were no issues with stability.

There was no issue with scalability.

We have not used technical support. The community is large enough to find the solution when something comes up.

We used many SQL database solutions like PostgreSQL and SQLite and NoSQL databases like MongoDB. The choice depends on the project.

The initial setup was straightforward.

I think that the Open Source product would cover the needs of most projects. In some cases, the advanced features are needed. They could use the enterprise edition, which is reasonably priced.

We have evaluated and used different products like SQLite. It depends on the requirements and the needs of the project.

I believe that it is the ideal solution for a variety of projects with a small learning curve compared to other solutions. It allows you to be efficient quickly.

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.

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.