It’s a feature preview with many limitations, but this is still good news. This has been a pretty severe performance limitation for replication in MySQL, which has prompted many a workaround. Interestingly, the feature preview is based on MySQL 5.1, which has recently seemed to be getting some significant changes even though it’s a GA release. Does this signal a change to MySQL’s release cycle, which has sometimes been characterized as too long?

I’m presenting about Maatkit, the toolkit I created to make life better with MySQL, at the MySQL conference next week. I’m going to give you a whirlwind tour through some of Maatkit’s features and functionality. The toolkit is much too large and complex to cover more than a small part of it in depth. So here is your advance warning: I’m going to go through a lot of material, and I won’t be stopping for lengthy discussions :-) The Maatkit documentation is very thorough, and I hope to introduce you to things that could be of use to you, so you can go learn about those topics from the documentation.

Having written about what I think is cool about the upcoming MySQL Conference and the MySQL Camp, now I want to finish up with what I’d like to see at the Percona Performance Conference. Just to recap, this is a conference we created to serve those who want to learn about performance – not “learn about MySQL,” not “learn about database performance,” just learn about performance, period. I want to see everything.

We were at the University of California, Berkeley, yesterday. Dups picked me up from the Hyatt, and we headed out there (despite the traffic jams caused by the major winds the night before — 50+mph winds!). Lunch was in Berkeley, and we met up with our Sun counterpart who deals with University Relations.

At about 3.50pm, we were told that our talk which was scheduled from 5-6pm, was actually meant to be at 4-5pm. Oops. I immediately sent a text message to Farhan, and he told me he was a few minutes away.

While the attendees all sat down and ate the pizza, we put on a little show for them, and then started at about 4.10pm. Farhan walked in a …

Recently, I was asked if it is possible to replicate an NDB cluster to a non-NDB MySQL database. So, I tried!

I created the following table on the MySQL master:

Create Table: CREATE TABLE `testrepl` (
  `id` int(11) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=ndbcluster DEFAULT CHARSET=latin1

and on the slave:

Create Table: CREATE TABLE `testrepl` (
  `id` int(11) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

Of course, for obvious reasons, NDB only supports row based replication so I configured the master to use row based:

mysql> show global variables like 'binlog_format';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| binlog_format | ROW   |
+---------------+-------+
1 row in set (0.00 sec)

Then I tried and go the following error:

Last_Error: Error 'Incorrect information in file: './mysql/ndb_apply_status.frm'' on opening tables …

Installing MySQL Connector/C++ from Source is the title of a Developer Zone article published today. Knowing how to build the driver from source is important to know for users of the MySQL driver for C++. C++ binaries are less portable than we would wish. There are reasons for incompatibilities beyond our control (different STL version, different compiler versions, …). If your system is not compatible with the build system we use for creating binaries, you may be forced to build the driver from source. I hope we do listen properly to you, if ….

The DevZone article has been written by Giri Mandalika. Giri has been introduced to me by …

Re: the title.

Explosive data growth has become problematic for traditional dbms architectures, and the creation of automated data factories (web logs, web transactions, micro transactions, RFID) that create new data every click/second/fractional second have applied further pressure on traditional approaches.  

Traditional approaches that rely on tables and indices can have interesting problems when the size of a table or index can exceed currently available memory.  Table scans that rely on physical I/O can be expensive in terms of both time to execute and the cost to scale I/O performance.  However, the fundamental inefficiency of executing a 'select *' from storage to satisfy a 'select 4 columns from some range of rows' becomes truly problematic when the wasted I/O is measured in terabytes.  Traditional index operations can have a more subtle, but potentially more dramatic impact on performance if …

Installing MySQL Connector/C++ from Source is the title of a Developer Zone article published today. Knowing how to build the driver from source is important to know for users of the MySQL driver for C++. C++ binaries are less portable than we would wish. There are reasons for incompatibilities beyond our control (different STL version, different compiler versions, …). If your system is not compatible with the build system we use for creating binaries, you may be forced to build the driver from source. I hope we do listen properly to you, if ….

The DevZone article has been written by Giri Mandalika. Giri has been introduced to me by …

During the event, I will do …

Q4M 0.8.5 is now downloadable from q4m.31tools.com. Prebuilt binaries for MySQL 5.1.33 running on linux (i386 or x86_64) and Mac OS X 10.5 (x86) are available as well.

There are no bugfixes in this release. The only change from version 0.8.4 is bundle of boost header files necessary for building Q4M. The build process no more requires separate installation of the Boost C++ libraries.