Extract from THE SCALE-OUT BLOG by Robert Hodges (CEO, Continuent)http://scale-out-blog.blogspot.com Data management is undergoing a revolution. Many businesses now depend on data sets that vastly exceed the capacity of DBMS servers. Applications operate 24x7 in complex cloud environments using small and relatively unreliable VMs. Managers need to act on new information from those systems in

In a world driven by computers, most companies rely on systems that are entirely built around databases. Losing data, or even as little as losing the full control over it, could bring any business down. Frequently databases hold sensitive information such as personal details, transaction statements, credit card data – among many other things. This is also why running certain types of databases is regulated in many countries by local as well as international laws – especially in Europe.

What is at stake?

• Availability. When a database or data disappear, business stops. Assuming you have working backups you can restore from, this is the least of all concerns.
• Confidentiality. Your secrets, private information of your customers and anything else that you decided not to make publicly available may be leaked.
• Privacy. Personal …

Thousands of new online and mobile apps launch every day…but what happens when demand climbs and databases can’t keep up?

  Matt Aslett of 451 Research will discuss:

Scaling-out your MySQL databases New high availability strategies Centrally managing a distributed MySQL environment

Matt is the Research Director for Data Management and Analytics at 451 Research, covering operational and analytic databases, with a [...] Read More

The MySQL team seems to have a very peculiar idea about defaults and compatibility. Recently, I wrote about an annoying warning that cannot be removed. And previously, I noticed that MySQL 5.6 mixes warnings, info lines and errors in the same bunch of excessive chattiness.

With MySQL 5.5.30 came another headache. When I run a mysqldump of the 'mysql' schema, I get this warning:

$. mysqldump mysql > m.sql
-- Warning: Skipping the data of table mysql.event. Specify the --events option explicitly.

OK. No big deal. What if I tell the little troublemaker that I DON'T WANT the events table?

$ mysqldump --skip-events mysql > m.sql
-- Warning: Skipping the data of table …

MySQL 5.6 is the latest production-ready release of the most popular opensource database management system on the planet ie. MySQL.

With MySQL 5.6 just gone GA, I thought it would be good to take a look at the changes in options and variables that comes with the new release.

First of all, several of the existing options have get new default values. As James Day already have written a good post about that in his blog, I will refer to that instead of going through the changes. For a general overview of the new features and improvements, the recent blogs by Rob Young and Peter Saitsev are good starting points together with the …

An old Chinese curse says "May you live in interesting times".
Fortunately this can be taken both as a curse or as a blessing.

For MariaDB this has definitely been a blessing the last few months.

Since we announced the MariaDB foundation in December 2012 a lot has happened:

• Wikipedia is moving to MariaDB.
• Mozilla is also now using MariaDB.
• Fedora and OpenSuse is replacing MySQL with MariaDB in their distributions.
…

A new version for Connector/Net 6.6 has been released. This new 6.6.5 version includes several new features that support the new capabilities included in MySQL Server 5.6, which recently has became at GA state.

Do you have the background necessary to take full advantage of Tungsten Replicator in your environments? Tungsten offers enterprise-quality replication features in an open source package hosted on Google Code. This virtual course will teach you how to set up innovative topologies that solve complex replication problems.

We start with a list of the main problems that Tungsten can solve, then

MySQL makes it easy to bulk load multiple rows of data from a flat file into a MySQL table using the LOAD DATA INFILE command, but that command can quickly get you into trouble if you are not careful about capturing the warnings and errors it produces.

Running LOAD DATA INFILE commands at the mysql prompt gives you pretty good output, but if you run the same command at the terminal or in a shell script you have to do a little bit of extra work to capture the errors and warnings.

Here are a few techniques I use when I run LOAD DATA INFILE at the terminal or in a shell script:

1. Use double-verbose mode (--v) to capture the high level counts of Records, Deleted, …