I am now in San Francisco, tomorrow I'll be leaving town for Santa Clara and the MySQL User conference. If you are at the conference, say hello and if there is anything you want to talk to me about, do so, I'll spend my time out and about at the conference.
I am involved in 2 talks:

• On Tuesday at 11:55 I am doing an introduction to libmysqld. If have not used libmysqld, and are interested in what it is and how it can be used, pop by this talk. I will also demo a small libmysqld application, so you know what can be done. It's actually pretty cool.
• On Thursday at 11:55, me and Robert Krzykawski from bWin are to present some real-world experiences with HA for MySQL. I will do an introductory talk here, with some HA for MySQL basics, and then Robert will tell you about the real world. bWin games is a big user of MySQL and has quite a load on their systems, so …

The BoF schedule for MySQL Conference and Expo (2009) is now published. Lenz Grimmer, Sergei Golubchik, Tomas Ulin and myself will be available during a BoF which focuses on MySQL Community Code Contributions. Lenz will be moderating. For background material, you may start here.

The BoF schedule for MySQL Conference and Expo (2009) is now published. Lenz Grimmer, Sergei Golubchik, Tomas Ulin and myself will be available during a BoF which focuses on MySQL Community Code Contributions. Lenz will be moderating. For background material, you may start here.

The slides are written, uploaded and the code snippets work. I’m ready to present.

One of the topics will be merging binlogs which is what multi-master replication is all about on the low level. A common example is sharding where you have several masters which share the same table-structures, but store the data independently. This is great for scaling out, but tricky if you have to run a query over the full dataset.

The logfiles look like:

$ mysqlbinlog binlog-merge-1.log -s
SET TIMESTAMP=1240066015/*!*/;
INSERT INTO tbl VALUES ( 1 )
/*!*/;
SET TIMESTAMP=1240066017/*!*/;
INSERT INTO tbl VALUES ( 3 )
/*!*/;
# End of log file
ROLLBACK /* added by mysqlbinlog */;

and

$ mysqlbinlog binlog-merge-2.log -s
SET TIMESTAMP=1240066016/*!*/;
INSERT INTO tbl VALUES ( 2 )
/*!*/;
SET TIMESTAMP=1240066018/*!*/;
INSERT INTO tbl VALUES ( 4 )
/*!*/;
# End of log file
ROLLBACK /* added by mysqlbinlog …

The slides are written, uploaded and the code snippets work. I'm ready to present.

One of the topics will be merging binlogs which is what multi-master replication is all about on the low level. A common example is sharding where you have several masters which share the same table-structures, but store the data independently. This is great for scaling out, but tricky if you have to run a query over the full dataset.

The logfiles look like:

$ mysqlbinlog binlog-merge-1.log -s
SET TIMESTAMP=1240066015/*!*/;
INSERT INTO tbl VALUES ( 1 )
/*!*/;
SET TIMESTAMP=1240066017/*!*/;
INSERT INTO tbl VALUES ( 3 )
/*!*/;
# End of log file
ROLLBACK /* added by mysqlbinlog */;

and

$ mysqlbinlog binlog-merge-2.log -s
SET TIMESTAMP=1240066016/*!*/;
INSERT INTO tbl VALUES ( 2 )
/*!*/;
SET TIMESTAMP=1240066018/*!*/;
INSERT INTO tbl VALUES ( 4 )
/*!*/;
# End of log file
ROLLBACK /* added by mysqlbinlog */;

As …

While Calpont has been engaged with a number of members of the MySQL community over the past years, this will be our first wide presentation of our storage engine capabilities.

What if loading your big data for analysis was easy? How about simple scale-out for data warehousing that allows analysis of all the data using all the resources of a distributed system, while retaining the simplicity of a single MySQL instance? How about blindingly fast analysis of the raw data without requiring aggregation that can lose the detail? Come find out what Calpont can offer: 

Calpont's foundation or Pillars:

Capable:
   - Purpose built for analytics
   - Built for big data
   - Built for speed

Scalable:
  - Scalable scan, filter, aggregation, and hash join
  - Intra-server parallelism (multithreaded within …

This is a “first-timer’s” guide to the MySQL Conference & Expo 2009. It is by no means official, but are things I think are somewhat important. Its broken down into sections: What days to attend, What to bring, Laptop, Blogging, Twittering, etc…, Be Social, The Attendee Directory, Evenings, and Did I miss something? Its long, but do bear with me — its just some friendly advice after attending this conference for quite the number of years.

What days to attend

The conference runs from Monday to Thursday. Monday is tutorial day, and Tuesday, Wednesday and Thursday are days where you have the conference proper.

Tuesday and Wednesday are days the Expo Hall is open. Go there, visit the place, learn about the ecosystem, and probably walk away with goodies while you’re at it. Don’t forget the DotOrg Pavilion, as there are plenty of open source projects …

I’m very proud to share with you a few things: Sheeri K. Cabral, Nick Westerlund, Paul Vallée, Peter Ling, and I (Augusto Bott) will be in Santa Clara, CA for the MySQL Conference and Expo, MySQL Camp, and the Percona Performance Conference, next week.

Nick and I will be presenting a session called Proactive Operational Measures on the Percona Conference, and another session called 8 Rules for Designing More Secure Applications at the MySQL Camp.

Sheeri will be presenting Understanding How MySQL …

A couple of years back, MySQL embarked upon a strategy to be more open and encourage third-party companies to create their own pluggable storage engines.  The strategy was partly a response to Oracle's acquisition of InnoDB, which was at the time the leading transactional storage engine.  Since then, we've seen new storage engines announced and released every year, typically at the April MySQL Users Conference.

read more

I am thrilled to announce that this year’s MySQL Conference will feature a Community Keynote. This is a keynote speech delivered by a community member (not a Sun employee!) about topics relevant to us.

I am delivering this year’s keynote, entitled “How to be a MySQL Superhero” on Wednesday, April 22nd at 9:45 am Pacific. Details are at http://www.mysqlconf.com/mysql2009/public/schedule/detail/9098. This is a great indication that Sun and O’Reilly are taking community very seriously, and want to make sure that our voices are heard — literally.

I hope that this can be an annual featured keynote, like the “State of the Dolphin.” The thriving community is one of the reasons MySQL is the world’s most popular database.