MySQL Reviews

We use MySQL to store data for our customers, in the database. It is a service-related application. Also to configure the data.

The fact that it is free is what appeals to me the most.

Scalability could be improved.

We use MySQL, which is a component of Oracle but operates as a separate database.

We have been using MySQL for more than ten years.

We are not using the most recent version, but rather one that has been tested with our applications.

We don't always use the latest version.

MySQL is a stable product.

It is very scalable. There are third-party solutions to assist with scaling but that may cost money, or it is available in the Commercial edition of MySQL.

We are primarily interested in Red Hat technology. As a result, we have primarily worked with Red Hat products.

This virtualization is built into Red Hat Hyperconverged Infrastructure.

We use both Red Hat Enterprise Linux, and Red Hat Hyperconverged Infrastructure.

The installation is straightforward.

We are using the free community edition of MySQL.

Definitely, I would recommend this solution to others.

I would rate MySQL a seven out of ten.

I use MySQL for employee service in an OLTP database.

I use MySQL for various purposes. Sometimes I have used MyISAM as a storage engine rather than InnoDB.

When working with a cluster wide, I have to use the MySQL cluster version.

The 5.7 version has very better performance improvement over the previous version.

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

This product’s most valuable feature to me is active-active (multi-master) cluster support for MySQL.

We have been using the multi-master solution from the Percona cluster. It seems to work as expected.

We use it as an embedded component of a solution we sell. It has provided a low-cost, high-availability solution without complex active/standby management using Linux HA.

It should provide detailed debugging with transaction IDs at the application level to understand deadlocks, especially under bursty workloads.

It should also provide partitioned tables and a clustered index, like Oracle, to take advantage of inherent parallelisms in the application domain.

It does not scale well when there are concurrent requests. Making changes to binlog and transaction log settings improves scalability at the cost of reliability.

It has decent support.

This product’s active-active cluster feature was the reason for choosing it.

One of the reasons PostgreSQL was not considered – a decision taken before I joined the company - was its lack of mature multi-master cluster support. It also lacked other popular ports (e.g. MariaDB, Percona, etc. in MySQL).

Ensure that it meets your scaling needs, and has features for handling parallelism in the application.

• Privileges
• Command line

I don't have any as this was my first time using it.

I think it is where it needs to be. MySql PaaS. But, you do need to have experience with SQL to use it.

I've used it for 12 months.

There were no issues deploying it.

It has been perfectly stable for us.

We've been able to scale it without issue.

4/10

7/10

MS Access. It wasn't compatible with my project.

It was a straightforward set-up.

We used an in-house team.

We also looked at Microsoft SQL Server.

Experience with SQL is vital. It is simple to learn and use.

At this time, pricing and footprint.

This database enabled us to web present our content in a cost efficient way.

I am not up to date on this issue.

At the time pricing and footprint.

This was the IT consultant's task to solve.

No issues encountered.

Not really, as our DB was small. With time, we got version issues, as our DB engine was so old and not updated.

I've never used it.

I've never used it.

No previous solution was used.

I don't know as we had consultants.

Consultant team.

We installed it under another now-obsolete license form (free on Linux).

No, as it was required for a CMS we implemented.

• Reliability
• Security
• Flexibility
• Functionality
• Availability - controllability anywhere and with different methods

MyISAM tables could be more reliable.

I've been using the Workbench Server for six years.

I have had no problems deploying it.

I have no stability problems.

I currently do not need to scale on my network.

I only have the free version, which does not have customer service.

I only have the free version, which does not have technical support.

We use Cisco ASA and Nagios devices alongside the MySQL server as our network infrastructure needs expanding and required more serious hardware solutions.

I believe it is hard to calculate for hardware.

I only use the free version.

We also looked at PostgreSQL.

As a rule, any device upon delivery is obsolete. Pick up the solution for your business, based on your specific needs.

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*