In June, I told about the consolidation of the MariaDB project tools. The final piece of this consolidation, to report bugs in the MariaDB project tracking tool called JIRA has now been finalized.

Bug reporting stays open! JIRA is open to anyone. The bug reports are publicly available, even without logging in and as a bonus it will be easier to follow what is going on in the project since you don’t have to jump between several tools to get the complete picture.

All bugs that existed in Launchpad have been migrated to JIRA. To find a bug that was originally reported on Launchpad use the following approaches:

• If you happen to have the original bug id you can search for the bug by typing lp:bugid into the search field in the upper right corner of JIRA. Also, if you have the …

At this weeks MySQL Connect conference, Oracle previewed an exciting new wave of developments for MySQL Cluster, further extending its simplicity and flexibility by expanding the range of use-cases, adding new NoSQL options, and automating configuration.

What’s new:

• Development Release 1: MySQL Cluster 7.3 with Foreign Keys
• Early Access “Labs” Preview: MySQL Cluster NoSQL API for Node.js
• Early Access “Labs” Preview: MySQL Cluster GUI-Based Auto-Installer

In this blog, I'll introduce you to the features being previewed.

Review the blogs listed below for more detail on each of the specific features discussed.

Save the date!: A live webinar is scheduled for Thursday 25th October at 0900 Pacific Time / …

MySQL Enterprise Backup(MEB) does hot backup of innodb data and log files. Till MEB 3.6.1, the user backs up the only innodb tables in a 3 step process:

STEP 1. Take backup using --only-innodb option

STEP 2. Temporarily make the table read only by executing “FLUSH TABLES WITH READ LOCK”

STEP 3. Manually copy the .frm files of innodb tables to the destination directory where backup is stored.

MEB 3.7.0 has an enhancement to innodb file copying. The .frm files gets copied along with the hot backup done for innodb files. I would like to make the blog a little interactive by explaining the feature as answers:

1. What are these .frm files?

The files containing the metadata, such as the table definition, of a MySQL table.

For backups, the full set of .frm files are always required …

I presented a webinar this week to give an overview of Tools and Techniques for Index Design. Even if you missed the webinar, you can register for it, and you’ll be emailed a link to the recording.

I’d like to invite folks who are interested in tools for query optimization to attend the new Percona online virtual training Analyzing SQL Queries with Percona Toolkit, October 29 – November 2, 2012. See http://store.percona.com/catalog.php?category=17 for details on this training class and how to register to attend.

During my webinar, I got a number of good questions. Here are the questions (paraphrased), with my answers.

Q: Can you link to the …

Last Month the Verizon folks asked for a presentation on MySQL Replication and so we will have one on Monday October 8th.  MySQL Replication is easy to setup, reliable, and MySQL 5.6 brings some new features such as Global Transaction Identifiers.  So some learn the basics and learn the new features. 

Starts at 5:00 PM! Please do not be late as the doors lock at 5PM and we will have to send someone to check on you!

Refreshments will be served!

Dallas – Irving Connection
6031 Connection Drive
Suite 900
Irving, TX 75039
Phone +1.972.652.8000

I yesterday finished the work for the first version of multi-source replication for MariaDB.

I first want to thank Peng Lixun at Taobao for giving us the code that I used as a base for this patch. Their patch worked and was used in production, but didn't have all the features needed for a 'full solution'. I have now added those.

Typical use cases for multi-source replication are:

• You are partitioning your data over many masters and would like to get it all together on one machine to do analytical queries on all data.
• You have many databases spread over many MariaDB/MySQL servers and would like to have all of them on one machine as an extra backup.

The new syntax introduced to handle …

Internet was born from static pages. People were creating websites with emacs and vi. With increased popularity of scripting languages and open source databases like MySQL and Postgresql, more and more developers started to use these advanced tools.

CMS systems were build. They made our lives much easier. Instead of altering file contents with editor, the user can simply go to the website admin

Cross-site databases are the next challenge facing today's MySQL-based businesses. Continuent Tungsten provides multiple options for spreading data across sites, including primary/DR, multi-master, and system-of-record approaches. Join us to learn how Continuent Tungsten enables replication, failover, and routing of transactions between sites.

We cover the following topics:

Introduction to

I will be speaking on Saturday, October 6th at the Silicon Valley Code Camp on MySQL Replication and The Proper Care and Feeding of a MySQL Database for Linux Administrators. And then a few days later it is down to Austin for Kuali Days. Please be sure to say ‘hi’ is you are attending either event.

In prior years a daily update from Open World was possible, but this year my schedule was too full to support it. This is my compendium of thoughts about MySQL Connect, JavaOne, and Open World 2012.

MySQL Connect was great – good sessions re-enforcing the positive investments Oracle is making in the product. I’ll leave to others to qualify changes in what elements of technology are opened or closed along the road to a better MySQL. The announcement of Connector/Python 1.0 GA on Saturday was great news and as a community we owe a lot to Greet Vanderkelen.

NoSQL is a hot topic along with using JSON objects and it was interesting hearing of some unequal testing paradigms to position non-Oracle solutions to be “better” …