MySQL Reviews

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

Customer Service:

4/10

Technical Support:

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.

Customer Service:

I've never used it.

Technical Support:

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.

Customer Service:

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

Technical Support:

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*

It is the database for a web application. I am using it for personal and official purposes.

It is easy to use.

It is not as powerful as SQL Server. It can be more powerful.

It is not scalable and has certain limitations, which is not the case with SQL Server.

I have been using this solution for a couple of years.

It is stable.

It is not scalable. We have around 10 to 15 web developers who are currently using it.

I have not interacted with them.

Its installation is not very complex. It takes two hours.

I installed it on my own. We have four or five people for deployment and maintenance.

For the on-premise version, no license is required.

We plan to keep using this solution. I would rate MySQL a seven out of ten.

On-premises

We use MySQL and MariaDB for most part of our mission critical applications

This as it is so simple to integrate with web applications, and other well known applications.

Since it has many integrations to web applications, it is very easy to install and deploy open source web applications.

How it uses clustering.

The API's to PHP, ruby, perl, java, python, and many more high level programming languages makes it easy for us to deploy new features fast.

How to scale out with shard clusters.

The way how to handle replications needs to be improved, as we noticed that there are some performance drop of (using only one core for example)

More than five years.

No issues.

Yes, the binary log replication process in a cluster environment has issues processing data as fast as it arrives.

Customer Service:

A 10 out of 10.

Technical Support:

A 10 out of 10.

We have been using many different types of databases, and will most likely use this one for part of our systems, as it is has so much integration.

The initial setup was easy.

We implemented it in-house.

Free.

Be sure to take backups of the solution, as this will check that the blocks are okay.

We decided to use "DB Protection for MySQL" as it has options to perform block level incremental forever, and integrates well with Spectrum Protect.

Yes, we checked MongoDB, PostgreSQL and MariaDB.

• It is inexpensive as compared to other common databases like Microsoft SQL Server or Oracle. • MySQL is an extensible, open storage database engine that integrates seamlessly with a number of programming languages and other web-based technologies. • MYSQL is an open source system under the GNU General Public License. Developers can use it at no cost as long as the associated projects are also open-source. • Having excellent performance, MYSQL is used by many internet powerhouses like yahoo as their back-end database. MYSQL has great performance due to format of its default table, MyISAM. MyISAM databases use little disk space, memory and cpu. The system runs without flaw and perform better on all platforms including windows, Unix and Linux.

• MySQL has a limited storage capacity. It doesn’t support large databases. • Database transactions are not handled efficiently. • Unlike Oracle, MySQL doesn't have Tablespace, Role management, snapshots, synonym and packages. • For transferring data, MySQL doesn’t support other languages being executed from within the system, and neither does it supports XML. • Compared to Oracle, MySQL database does not support any feature like Audit Vault on its server • There is a limited scope and earning available for database administrator of MySQL.

MySQL is an open source database management system and is used by most of the most famous networking sites. It is more popular in websites and PHP integration. It can be executed under a number of operating systems like Linux, UNIX, Mac OS and Windows. MySQL supports ODBC interface which allows MySQL to be addressed by all the usual programming languages that run under Microsoft Windows.

It depends on the use and implementation, as I prefer to use Galera or XtraDB because of replication and failover functionality. However, the ability to scale horizontally is much better than other vendors. Also, the transactional functionality is good.

Configuration templates and reliability both need work.

I have been using MySQL for over five years.

I deploy multiples of these servers now, and it is all managed via a puppet so I/we have not had problems with deployment in a long time.

An overload of sessions, or long running queries. can cause the servers to be unusable.

Currently no, as we use our own load balancer to enable us to scale to any level.

We don't use it.

It was straightforward, and there are numerous blogs on-line that cover every possible configuration.

We did it in-house.

It takes about six months, but this does depend on its associated product and usage.

Chose your database based on traffic type and desired functionality, not on the initial cost.

If you have the in-house knowledge MySQL can be a great product. If you do not I would recommend using MSSQL instead.

Take a look at the environment you plan to implement including the application and traffic model.