(Jay Janssen) MySQL 5.6 upgrades are in full swing these days and knowing how to safely upgrade from MySQL 5.5 to 5.6 is important. When upgrading a replication environment, it’s important that you can build a migration plan that safely allows for your upgrade with minimal risk — rollback is often a

(Shinguz) The MySQL Backup Manager (mysql_bman) is a wrapper script for standard MySQL backup tools. The Problem with MySQL backup tools is, that they have many options and thus are overcomplicated and errors are easy made.

(Tim van der Linden) Welcome to the second installment of our look into full text search within PostgreSQL.

(Dave Stokes) There was a on Twitter to @MySQL How can I insert “/” into a varchar field please. Since they were polite and used please, I wanted to be helpful.

(Craig Kerstiens) Postgres has a variety of datatypes, in fact quite a few more than most other databases. Most commonly applications take advantage of the standard ones – integers, text, numeric, etc. Almost every application needs these basic types, the rarer ones may be needed less frequently.

(Muhammad Irfan) Here on the Percona MySQL Support team, we often see issues where a customer is complaining about replication delays – and many times the problem ends up being tied to MySQL replication slave lag.

(Josh Berkus) As long as we’re overhauling standard monitoring queries for PostgreSQL, here’s another one. This query helps you find indexes which are relatively unused, and as a result could probably be dropped. I wrote a more complex (yes, really) version for our internal Performance Health Chec

(Giuseppe Maxia) MySQL, the original brand, the one developed by the MySQL team at Oracle, is steadily evolving. You can feel it if you try every new release that comes out of the milestone release cycle. Or even if you don’t try all of them, just testing a release once in a while gives you somethin

(Marko Tiikkaja) Often on the topic of the different JOIN syntaxes in SQL I mention that I consider ON the only reasonable way to specify JOIN clauses in production code, and I get asked for details. It always takes me a while to recall the specific problem and to come up with a plausible scenario,

(Ike Walker) Before upgrading from MySQL 5.5 to 5.6, I read the relevant page in the reference manual and found this section about the storage format change for DATETIME, TIME, TIMESTAMP data types to support microseconds: