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.

MySQL is an Open Source RDBMS, which means you keep your costs low, as long as you don’t need to have support and/or you have your own MySQL expert. However, MySQL also offers the enterprise edition for users that would like support and more advanced features.

When it comes to features, MySQL offers all the features of a RDBMS system, including monitoring tools, backup and recovery, high availability and easy migration from other databases.

For any web project today you are going to need a database system. If you use any Content Management System, MySQL is most of the times the database of your choice.

MySQL is easy to use, most developers have experience using it and it is an Open Source, cost-effective solution.

Although MySQL should cover most of the needs of an average user, there are constrains that need improvement.

For example, MySQL doesn’t support check constraints. MySQL’s performance is not optimal on subqueries and can significantly increase the server load for database intensive applications.

Another issue is the ineffective table manipulation during multiple transactions which result in implicit Commits.

Finally, since MySQL is now part of Oracle, and Oracle already sells their own databases, changes and bug fixes have significantly slowed down for obvious reasons. Oracle cannot improve MySQL too much, since it will then compete with their commercial database systems.

We have been using MySQL either through custom projects or through CMS, for more than 15 years now.

We haven’t encountered any serious stability issues with MySQL.

However, as with all systems, you need to keep your database “tidy”, making sure to optimize it, clean it and avoid corrupt files.

For critical projects, it may be wise to have redundancy by having two servers synced all the time.

Most scalability issues with MySQL can be simply resolved by adding more memory, optimizing settings or moving to a better server.

Of course, if you are talking about 40-50TB of data, or critical applications, then you will probably need to move to a more commercial database, such as Oracle.

We haven’t used the enterprise edition of MySQL, since most of our projects do not require such support levels. Most issues are handled by our developers.

MySQL has been the only solution for all of our web projects.

Setting up MySQL is simple, however, optimizing it requires some experience which is also based on the demands of each customer.

When we started using MySQL, it was more or less the best Open Source RDBMS for web projects. Today, you have multiple options, such as PostgreSQL, SQLite and MariaDB, therefore the choice for a newcomer should be based on their project needs.

For us, MySQL is the choice for all of our projects. It is simply to use, supported by all content management systems and, of course, Open Source.

We haven’t had any major issues, and since we have now developed MySQL technical skills and custom libraries, there is no reason to move on with a different RDBMS, unless circumstances change.

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.