Last week I blogged about a patch for Sphinx 0.9.8.1 that allowed Drizzle to be used as a data source (this works much like the MySQL and PostgreSQL options). This past weekend I made a new patch that would work with the latest version, 0.9.9-rc2. It can be found here:

sphinx-0.9.9-rc2-drizzle.patch

The instructions are pretty much the same:

Download sphinx-0.9.9-rc2.tar.gz and sphinx-0.9.9-rc2-drizzle.patch
tar xzf sphinx-0.9.9-rc2.tar.gz
cd sphinx-0.9.9-rc2
patch -p1 < ../sphinx-0.9.9-rc2-drizzle.patch
./buildconf.sh
./configure --with-drizzle
make
make install

See my previous blog post for configuration changes to make Sphinx index from Drizzle. …

The beginning of this story is coming from the first weeks of the last year - seeking for the most optimal MySQL config parameters I've discovered a strange thing:

• my dirty pages percentage setting 15 was completely ignored by InnoDB during my tests!...
• once the test workload was finished it still took 30 minutes yet to flush dirty pages!...

I've told about a lot of people on that time, but everybody were just surprised and did not really believe such case is possible... Agree, it's hard to believe ;-)

So, to refresh the story, let me first to show you the following picture:

As you may see here the dirty pages percentage is higher than 15% for sure :-) As well you may see the 30 minutes of dirty pages flushing once the workload is finished (too much according to me on the idle server! - and probably recovery process will take even more time if my server will crash?...)

…

Our lastest Alpha2 release of MySQL Workbench 5.2 made it pretty clear that one of our main goals for WB 5.2 is to replace the old MySQL Query Browser (QB) tool.

Even this Alpha2 release already covers most of the essential QB functionality, while at the same time removes some of the biggest limitations that the old QB tool suffers from. Here is a short list of the most important features.

MySQL Workbench 5.2 Features replacing QB

• Database Connection management
• SQL statement editor with syntax highlighting
• Edit multiple statements at the same time (scripts)
• Editable result sets for table data
• Database Schema browsing

New MySQL Workbench 5.2 Features

• Intuitive Database Connection listing on Home page and direct access to SQL Editor
• Ability to open SQL Editors for many different connections at the same time
…

There are times when you don't need a MySQL server to handle your queries, this could come handy when you are automating tests, or writing interesting Lua scripts.

Yes, you can use the MySQL Proxy for this as well. And have it pretend to be a MySQL server.
Today we'll focus on a simple implementation. We will handle an initial connection, a SHOW DATABASES query and the exit (QUIT) command.

You can see all the hooks that the proxy handles on this Lua script written by Giuseppe

Connecting to a server. …

This Thursday (May 28th, 14:00 UTC), Lars Thalmann will give a MySQL University session on MySQL Replication: Walk-through of the new 5.1 and 6.0 features. (This session was originally scheduled for May 7th, but had to be put off due to technical problems. Apologies.) Lars is leading the replication and backup teams at MySQL, so this is one of the best opportunities to ask whatever questions you might have about new replication features in MySQL.

For MySQL University sessions, point your browser to this page. You need a browser with a working Flash plugin. You may register for a Dimdim account, but you don't have to. (Dimdim is the …

It is getting summer in Germany: let’s have a PHP BBQ tour! The PHP BBQ tour is one week tour from Monday, 15.06. - Sunday, 21.06.2009 visiting the german PHP user groups. The tour will go through Munich, Frankfurt, Karlsruhe, Berlin, Dortmund, Hamburg and Kiel. The tour is an offering and a suggestion to the user group to come together for a barbecue instead of meeting in conference rooms in the middle of the summer, when the days are long. Everybody is invited to join me and other MySQLers on the tour to visit the PHP user group in his neighbor town.

It is getting summer in Germany: let’s have a PHP BBQ tour! The PHP BBQ tour is one week tour from Monday, 15.06. - Sunday, 21.06.2009 visiting the german PHP user groups. The tour will go through Munich, Frankfurt, Karlsruhe, Berlin, Dortmund, Hamburg and Kiel. The tour is an offering and a suggestion to the user group to come together for a barbecue instead of meeting in conference rooms in the middle of the summer, when the days are long. Everybody is invited to join me and other MySQLers on the tour to visit the PHP user group in his neighbor town.

I have been busy lately thanks to my internship project, which almost got screwed up. I was working in a team of 4 people, where we were building a web application, that was initially deployed at JBoss Server using JBoss Eclipse IDE (old version). Also, we had to interact with the centralized Oracle Server to setup our database for running the website.

Now, having being trained on some of those technologies in past few months, I thought it won’t be much of an issue. However, at the beginning of this month, I faced some weird issues which had no obvious answers. There weren’t any silly mistakes either. We were facing some issues with Oracle connectivity. I am not blaming Oracle or the company where we did the project. But, mix of old and new technologies, turned out to be quite confusing resulting in lot of trouble.

We were running out of time, so we decided to migrate our database to MySQL Server and use NetBeans 6.5 IDE, …

Last weekend I’ve reached a milestone in my work on the statistical index analysis for QOT. The code is available on Launchpad.

An example is worth a thousand words, so I start with one (once again I’m using employees-db):

$ ./qot –info –host=192.168.200.1 –analyse=possible –schema=employees –query=”select * from dept_emp where (dept_no = ‘d005′ or dept_no = ‘d006′) and (emp_no = 10010 or emp_no = 10011)”

/* Output produced by qot 0.1.6 GPL */
/*
Query: select * from dept_emp where (dept_no = ‘d005′ or dept_no = ‘d006′) and (emp_no = 10010 or emp_no = 10011)

selectivity:
all rows

used tables:
dept_emp (all rows)

ordering:
no ordering

related existing indexes:

…

A bug in libcurl affects how the heartbeat function of MySQL Enterprise Monitor works by sending it to an external website, often www.agent.com.