If you require to get all the records of current year using mysql query for example you have one table items and columns are id title description createdat and updateat Now you want to get all records of this year so you can fetch fields value using DATESUB and INTERVAL of mysql In follo

If you require to get all the records of current year using mysql query for example you have one table items and columns are id title description createdat and updateat Now you want to get all records of this year so you can fetch fields value using DATESUB and INTERVAL of mysql In follo

In this post, we’ll look at scaling Percona XtraDB Cluster with ProxySQL in Docker Swarm.

In my previous post, I showed how to employ Percona XtraDB Cluster on multiple nodes in a Docker network.

The intention is to be able to start/stop nodes and increase/decrease the cluster size dynamically. This means that we should track running nodes, but also to have an easy way to connect to the cluster.

So there are two components we need: service discovery to register nodes and ProxySQL to handle incoming traffic.

The work with service discovery is already bundled with Percona …

MySQL 5.7 has been GA since October 2015. At the time of writing, it is still a very new release. But more and more companies are looking into upgrading, as it has a list of great new features. Schema changes can be performed with less downtime, with more online configuration options. Multi-source and parallel replication improvements make replication more flexible and scalable. Native support for JSON data type allows for storage, search and manipulation of schema-less data.

An upgrade, however, is a complex process - no matter which major MySQL version you are upgrading to. There are a few things you need to keep in mind when planning this, such as important changes between versions 5.6 and 5.7 as well as detailed testing that needs to precede any upgrade process. This is especially important if you would like to maintain availability for the duration of the upgrade.

…

As Morgan announced it his blog post related to new defaults in 5.7, in 5.7.7 and newer the default value of sync_binlog is now 1.

This of course has an impact on performance especially if you don’t have fast storage like a RAID controller with a cache for example.

Already in O’reilly High Performance MySQL, is was written that the most important setting for binary logging on the master is sync_binlog = 1.

And this recommendation was made for MySQL 5.0 ! At that time the performance impact could reach 50%. In 5.6, with the addition of binary log group commit …

The MySQL developer tools team announces 6.3.7 as our GA release for MySQL Workbench 6.3. 

For the full list of changes in this revision, visit 
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html 

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/list.php?152

Download MySQL Workbench 6.3.7 GA now, for Windows, Mac OS X 10.9+, 
Oracle Linux 6 and 7, Fedora 23 and Fedora 24, Ubuntu 16.04 or sources, from:

http://dev.mysql.com/downloads/tools/workbench/ 

Enjoy!

Dear MySQL users,

The MySQL developer tools team announces 6.3.7 as our GA release for
MySQL Workbench 6.3.

For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?152

Download MySQL Workbench 6.3.7 GA now, for Windows, Mac OS X 10.9+,
Oracle Linux 6 and 7, Fedora 23 and Fedora 24, Ubuntu 16.04
or sources, from:

http://dev.mysql.com/downloads/tools/workbench/

Security auditing plays important role in the process of securing a database system. Thanks to the MySQL Enterprise Audit extension, we can record all activities, such as client connections and execution of queries into a single log file, for later inspection.…

Learning from facepalm moments of a MySQL database restore from Percona Xtrabackup.

The post MySQL database restore issues using xtrabackup – facepalm moments first appeared on Change Is Inevitable.

Docker is quickly becoming mainstream, as a method to package and deploy self-sufficient applications in primarily stateless Linux containers. But for a stateful service like a database, this might be bit of a headache. How do we best configure MySQL in a container environment? What can go wrong? Should we even run our databases in a container environment? How does performance compare with e.g. running on virtual machines or bare-metal servers? How do we manage replicated or clustered setups, where multiple containers need to be created, upgraded and made highly available?

So, welcome to our new blog series - “MySQL on Docker”. We will touch upon swarms, shared volumes, data-only-containers, security and configuration management, multi-host networking, service discovery and implications on monitoring when we move from host-centric to role-centric services with shorter life cycles.

In our first blog post, we are going to cover …