The first public mysqlnd plugin adds client side query result caching to all MySQL extensions of PHP (ext/mysql, ext/mysqli, PDO_MySQL). The cache is written in C. It does not change any of the PHP MySQL APIs and works with any PHP application using MySQL. Query results are stored on the client. Cached data can be stored in main memory, APC, Memcache, SQLite (theoretically - via SQLite …

The first public mysqlnd plugin adds client side query result caching to all MySQL extensions of PHP (ext/mysql, ext/mysqli, PDO_MySQL). The cache is written in C. It does not change any of the PHP MySQL APIs and works with any PHP application using MySQL. Query results are stored on the client. Cached data can be stored in main memory, APC, Memcache, SQLite (theoretically - via SQLite …

There's a lot of buzz lately about Hadoop. If you're completely new to Hadoop, I recommend the free videos from Cloudera (http://www.cloudera.com/resources/?type=Training). If you have a vague idea and want to play around, it's easy!
First, download Cloudera's training VM which has a small Hadoop cluster already installed and running: http://www.cloudera.com/developers/downloads/virtual-machine/
Second, you need to put some data into Hadoop. Fortunately for database folks, there's a tool to import data into Hadoop from MySQL called "Sqoop". It's already installed on the VM and there are instructions for using Sqoop to import some MySQL tables into Hadoop (see Desktop/instructions/exercises/SqoopExercise.html inside the VM). FYI, it's not uncommon to "Sqoop" data …

In MySQL, even though the name read_buffer_size implies that the variable controls only read buffering, but it actually does dual purpose by providing  sequential IO buffering for both reads and[...]

OpenSQLCamp is less than 4 months away, and I have finally gotten around to updating the site. Special thanks go to Bradley Kuzsmaul and the folks at Tokutek for getting the ball rolling and making the reservation at MIT. Using MIT means that we will have *free* reliable wireless guest access and projects.

OpenSQL Camp is a free unconference for people interested in open source databases (MySQL, SQLite, Postgres, Drizzle), including non-relational databases, database alternatives like NoSQL stores, and database tools such as Gearman. We are not focusing on any one project, and hope to see representatives from a variety of open source database projects attend. As usual I am one of the main organizers of Open SQL Camp (in previous years, Baron Schwartz, Selena Deckelmann and Eric Day have been main organizers too; this year Bradley Kuzsmaul is the other main organizer). The target audience …

It was funny to wake up to this article on "
Marten Mickos says open source doesn't have to be fully open".

I can remember the morning of the first keynotes for the MySQL Conference after Sun had acquired MySQL. You have Jonathan Swartz and Rich Green delivering keynotes where the underlying message was "we continue to allow MySQL to run its own business".

Why was this?

Because Marten was going to announce the close sourcing of part of the MySQL Server. For years there were conversations around "if we did XYZ could we take out a critical...". These conversations were always met with a dead silence. The codebase was neither modular, nor did any of the developers resonate …

Julie Bort of Networkworld.com has an interview with Mårten Mickos of Eucalyptus, formerly of MySQL. In MySQL times it seemed (to me at least) that most users never realized Mårten and his management team were taking MySQL increasingly into a closed source direction. (Maybe I'm just stupid myself, but at least personally I had not noticed this until after I started working for the company.) In this interview Mårten at least comes squarely out of the closet and is defending the model.

Julie makes a good journalistic effort of reporting on the topic from a neutral point of view. Alas, sometimes that approach just makes things fuzzier. So let me try to make one thing clear: Open core may be a good business model, but open core is not open …

Translation of chapter 5 which describes alternate methods for searching problem query just published. It starts like:

Chapter 5. Alternate methods for finding problem query.

I already wrote about using of general query log requires resources.
Part of the problem can be solved if use new feature of MySQL 5.1:
online logging which allows to turn general query log to on or to off
without stopping the MySQL server.

Unfortunately this doesn't always work: you can have old
version of MySQL server which has not such a feature, general query log
can contain very large amount of information, so you can just miss the
problem in thousands of correct queries, you can have some other own
reason.

But what to do if you can not use general query log?

…

At SQLstream, we have no doubt that streaming SQL and stream computing will be a key part of the next-generation enterprise infrastructure, but we are less certain how we fit into trends such as "Big Data" and "NoSQL".

Taking the terms absolutely literally, we aren't either. We can't be "Big Data" because we do out damnedest to process data as fast as we receive it, in memory. I guess "Fast Data" would be a better word for what we do. And we can't be "NoSQL" because we're the biggest cheerleaders for industry-standard SQL you'll find anywhere outside Redwood Shores or Almaden.

But we founded the company because we foresaw …

Translation of chapter 5 which describes alternate methods for searching problem query just published. It starts like:

Chapter 5. Alternate methods for finding problem query.

I already wrote about using of general query log requires resources.
Part of the problem can be solved if use new feature of MySQL 5.1:
online logging which allows to turn general query log to on or to off
without stopping the MySQL server.

Unfortunately this doesn't always work: you can have old
version of MySQL server which has not such a feature, general query log
can contain very large amount of information, so you can just miss the
problem in thousands of correct queries, you can have some other own
reason.

But what to do if you can not use general query log?

…