MySQL Enterprise Backup (MEB) supports backup and copyback of mysql database objects into/from different disks or tape drives. On backup, MEB reads the data from the disk, processes it in form of validation or compression(if requested by user) and writes to disk. These operations were performed in a serial fashion till 3.7.1, wherein the reading of data is completed, followed by processing, and then writing. The performance of this can be increased by pipelining the read, process and write operations to be run in parallel, and this is what exactly is done in the latest release MEB 3.8.0 so as to reduce the time taken for all kinds of backups and restore operations.

How does this pipeline parallelism work?

This pipelined parallel execution of read, process(if any) and write operations is achieved by invoking multiple threads for different operations and usage of buffers. Each operation is split into segments and threads …

http://datacharmer.blogspot.it/2012/08/is-oracle-really-killing-mysql.html

An insightful post for my former  (MySQL AB) colleague Giuseppe Maxia about how Oracle’s actions affect the MySQL landscape.

My own comment exploring why it’s happening (from Upstarta perspective) is on his blog post rather than here. From Open Query’s business perspective, we generally deploy MariaDB unless client prefers distro stock. We get the features we need in MariaDB, see the bugfixing and have an open dialog with the developers and see the development process.

While the current new code coming from Oracle definitely has interesting components, MariaDB has solved some real problems (such as subqueries), and integrated useful engines such as Sphinx, FederatedX, and our on …

I decided to take another look at MySQL 5.6, and realized that I’ve forgotten how many changes this version will have. Each milestone has many improvements, and there have been many milestones, so my memory of the older ones grows hazy. The Fine Manual has the details, but here is my attempt at a quick (and probably incomplete and inaccurate) summary. I’ve emphasized a few changes that will make life significantly better for me.

Last week I heard about a company that has a concern with their NoSQL solution and the replication of their data. I, of course, thought of the new MySQL 5.6 release as a possible solution for their problem.

You can combine all your data across the same nodes and replicate it very easily.  All the while the data is  accessible via SQL and NOSQL. MySQL Cluster proved this in MySQL Cluster 7.2 already, so now it will also be available for MySQL 5.6.

Some great blogs and documentation already exist on this topic but they are a little older:
…

For a long time I’ve been maintaining a set of scripts inspired by Giuseppe Maxia’s MySQL Sandbox, which is a Swiss Army Knife for starting and stopping server instances for jobs such as testing, development, trying out a new version, and so on. My scripts are unpublished, until now. I’ve just kept them in my Dropbox’s bin folder, which I add to my $PATH.

It’s not worth explaining why I use my own scripts, except for saying that I keep dozens or even more MySQL versions unpacked in my home directory at any given time, and I find it a little easier to use these lightweight scripts than the more fully-featured MySQL Sandbox tools.

Usage assumes some conventions are followed. I “install” each version of the server by downloading the generic tarball. Then I unpack it and move it to $HOME/mysql/servers/VERSION, where VERSION is something like 5.5.27. If it …

Creating Advanced MySQL-Based Virtual Hosts On Lighttpd (Debian Squeeze)

This guide explains how you can create advanced virtual hosts on a lighttpd web server on Debian Squeeze that are stored in a MySQL database. The method described here does not use the lighttpd mod_mysql_vhost module, and unlike mod_mysql_vhost (which allows you to store only the hostname and document root of a vhost in a database), this method allows to store individual configuration directives for each vhost in the MySQL database.

Someone recently asked me why the wrong index was being used for a JOIN, making the query run very slowly. We ran EXPLAIN and saw this abridged output:

explain select [columns] from m
   left join u on m.intcol = u.intcol and m.url = u.url
where u.url is null\G
*************************** 1. row ***************************
  select_type: SIMPLE
        table: m
         type: ALL
         rows: 2717
*************************** 2. row ***************************
  select_type: SIMPLE
        table: u
         type: ref
          key: idx_intcol
      key_len: 2
          ref: m.intcol
         rows: 64486
        Extra: Using where; Not exists

The column is a 2-byte unsigned integer. Here is the relevant part of the table definition:

CREATE TABLE `u` (
  `intcol` smallint(5) unsigned NOT NULL,
  `url` varchar(760) CHARACTER SET latin1 COLLATE latin1_general_cs NOT NULL,
  UNIQUE KEY `url` (`url`,`intcol`),
  KEY …

I don't know why SELinux problems seem so frustrating. The problem almost certainly is related to the fact that there is frequently no error message. This is exactly the problem I ran into while turning up a new Apache web server on Red Hat Enterprise Linux 6 (RHEL6) with SELinux enabled.

If you need 99.999% availability, real-time performance, auto-sharding and write scalability, geographic replication - using SQL and NoSQL applications then you should learn more about MySQL Cluster.

The authentic MySQL Cluster course brings you key conceptual and configuration information in a 3 day instructor led class.

Examples of class events already on the schedule:

There are plenty of "Oracle-is-killing-MySQL" headlines in the tech world:

• Oracle Makes More Moves To Kill Open Source MySQL
• Oracle now destroying MySQL
• Is MySQL Slowly Turning Closed Source?

Is Oracle really consciously and willingly killing MySQL?

I don't think so.

Is Oracle damaging MySQL by taking the wrong steps? Probably so.

This is my personal opinion, and AFAIK there is no official statement from Oracle on this matter, but I think I can summarize the Oracle standpoint as follows:

• There is a strong and …