As you probably know MySQL is an Open Source product licensed under the GPL v2. The GPL grants you the right to not just read and understand the code of the product but also to use, modify AND redistribute the code as long as you follow the GPL rules.

This redistribution has happened in the past various times. But in the western hemisphere only 3 of these branches/forks of MySQL are of relevance for the majority of the MySQL users: Galera Cluster for MySQL, MariaDB (Server and Galera Cluster) and Percona Server (and XtraDB Cluster).

Now it happened …

In 8.0 we have introduced another bunch of parser refactoring worklogs:

• WL#8067 (me): “Refactoring of the CREATE TABLE statement” with its subtasks:
  • WL#8434: Refactoring of partitioning-related stuff.
  • WL#8435: Cleanup and refactoring column definition stuff.
  • WL#8433: Separate DD commands from regular SQL queries in the parser grammar.

…

Apart from Oracle, MySQL and SQL Server are the most popular RDBMS in the software industry. Which database platform should you choose?

The post MySQL or SQL Server? appeared first on Datavail.

Join us on Tuesday, December 6th, for our last webinar of the year. Krzysztof Książek, Senior Support Engineer at Severalnines, will be sharing his top 9 tips on how to best build a production-ready MySQL Replication environment.

MySQL replication is a well known and proven solution for building distributed setups of databases, and it has gone through a total transformation with version 5.6 and more recently, 5.7. Although straight-forward to deploy, a production-ready setup requires a bit of planning and preparation. What does a good replication configuration look like? How do you ensure performance? What do you do when a topology is broken, and replication will not restart? How to perform schema changes?

So if you'd like to learn what is needed to build a stable environment using MySQL replication, this webinar is for you!

Top 9 Tips for building a stable MySQL Replication environment

Tuesday, December 6th …

Happy Thanksgiving!

This week is all about savings. If you have seen offers all around you, well… digest this before you dig into that turkey.

A never before offer, flat 30% discount on SQLyog & Monyog product purchases & upgrades. 

Use coupon code: TG30

Hurry up, this offer is valid until 24th November, 23:59 PST.

Are you using SQLyog community edition? It’s the perfect time to upgrade to the commercial version and use powerful tools to save tons of time on a daily basis. Shop here.

Want to become better at monitoring MySQL servers? Experience Monyog – the most secure & scalable MySQL monitoring tool. Know what’s in store for you.

If you’re an existing …

Whether for a maintenance, applying non dynamic config changes, MySQL upgrade or other many reasons, a MySQL shutdown/restart is required.
In this post I’ll list some of the best practices before shutting MySQL down to make it clean and fast which in turn, will lead to fast and safe start!

1. Double check the instance you are going to shutdown!!
   First of all, and before doing anything confirm first the instance you are going to shutdown. You definitely, don’t want to shutdown a wrong MySQL instance by mistake, especially, when you’re working on production environments.
2. Stop Replication:
   Although MySQL stops the replication automatically in the shutting down process but if it didn’t stop for any reason before the timeout is reached, it will be killed. So, if that server is a slave, it’s better to stop the replication threads first …

Percona announces the release of Percona Server 5.5.53-38.4 on November 18, 2016. Based on MySQL 5.5.53, including all the bug fixes in it, Percona Server 5.5.53-38.4 is now the current stable release in the 5.5 series.

Percona Server is open-source and free. You can find release details in the 5.5.53-38.4 milestone on Launchpad. Downloads are available here and from the Percona Software Repositories.

Removed Features:

…

MySQL continues to be one of the most popular databases used in cloud-native applications. In fact, MySQL is so popular that other cloud databases such as AWS Aurora maintain wire protocol compatibility with MySQL. For SREs and DevOps engineers running MySQL database in production, it is crucial to understand how to monitor MySQL. MySQL poor health can lead to cascading effects on other application components. For example, slow queries can impact page load times for an application, or missing indexes can result in high-latency and application time-outs. By effectively monitoring the performance of databases and query executions, SREs and DevOps can identify if there are bottlenecks in the database tier which affect the overall application performance. With this appreciation for the importance of MySQL monitoring, let us quickly survey what techniques are commonly used for MySQL monitoring and then discuss …

I’ve been a fan of GNU Parallel for a while but until recently have only used it occasionally. That’s a shame, because it’s often the simplest solution for quickly solving embarrassingly parallel problems.

My recent usage of it has centered around database export/import operations where I have a file that contains a list of primary keys and need to fetch the matching rows from some number of tables and do something with the data. The database servers are sufficiently powerful that I can run N copies of my script to get the job done far faster (where N is value like 10 or 20).

A typical usage might look like this:

cat ids.txt | parallel -j24 --max-lines=1000 --pipe "bin/munge-data.pl  --db live >> {#}.out

However, I recently found myself scratching my head because parallel was only running 3 jobs rather than the 24 I had specified. …

After MySQL version upgrade, there is a possibility that application will start getting error/exception for INSERT/UPDATE operation due missing default data/values as follows,

ERROR:  Field ‘column_name’ doesn’t have a default value

Also above error will trigger for the wrong data type or out of range value for the column with INSERT/UPDATE sql operation.

Reason for this error is new SQL_MODE default values (MySQL 5.7 ) that included STRICT_TRANS_TABLES value in it and sql_mode value in default my.cnf created after installation[ Under /etc/my.cnf or /usr/my.cnf ]