I can't write I'm just back from MySQL Users Conference both because I'm still in USA visiting customers and because it has ended almost a week ago but I was too busy to write anything about it or post my presentations.

This was my 5th MySQL Users Conference so I met a lot of good friends and spend more time speaking to people when expected (even though still did not speak to everyone I wanted to) and less time attending the sessions.

The Conference was solid and interesting this year while it was not so strictly organized as before. For example even though there suppose to be "Session Buddies" they did not show up on my sessions and on one of them I had to myself remind to Jim Starkey he was 10 minutes into my talk already. The fact all rooms were about the same size was also a problem - many interested sessions were jam packed while other rooms were empty. It is surely exciting to speak with standing audience but I'd prefer …

I was asked the question today, “How do I show the details of a Stored Procedure in MySQL. The SHOW PROCEDURE ‘name’ didn’t work.”.

The obvious answer was SELECT ROUTINE_NAME,ROUTINE_DEFINITION FROM INFORMATION_SCHEMA.ROUTINES, given I like to use the INFORMATION_SCHEMA whenever possible. This lead me to think was is the corresponding SHOW command. A quick manual search got me to SHOW CREATE PROCEDURE.

What was interesting was not this, but the list of other SHOW commands I didn’t know. I did not know about SHOW MUTEX STATUS, SHOW OPEN TABLES and SHOW …

Compiere fork ADempiere claims production quality. Unisys and Forrester release study on open source acceptance. Apelon open sources Vocabulary Server. (and more)

ADempiere becomes first true open source production grade ERP, ADempiere (Press Release)

Independent Research Firm?s Commissioned Study for Unisys Shows Growing Acceptance of Open Source in Business-Critical Applications, Unisys (Press Release)

Apelon Vocabulary Server Now Open Source, Apelon (Press Release)

Survey: open source shows progress in public sector, The Register (Article)

…

Matt’s post on managing the ‘No Open Source’ clause cites stats from the recent Forrester report that shows a perniciously high percentage of respondents are concerned with ‘legal liabilities for copyright and patent infringement” (43% if I read the data properly), and how a dual license strategy takes this issue off the table.

That all makes perfect sense.

But what if the reason dual license open source companies like mySQL are successful is because Enterprises overstate the real risk of using open source software!

Wouldn’t that be ironic: As Enterprises gain awareness and sophistication about open source licensing issues and IP, they become …

We’ve been doing a lot of performance analysis of MySQL and SATA disks over the last few days and I wanted to get some thoughts out in the open to see what you guys thought.

Now that Debian Etch is out we’re seriously looking at making the jump to a full 64bit OS with 8G of memory on each of our boxes.

This also involves benchmarking SATA and potentially migrating away from MyISAM which, while very trusty, is seriously showing its age for us.

First off is raw IO tuning.

XFS benchmarks show about a 20% performance boost from bonnie++ over ext3. This is pretty obvious. Tuning readahead with ‘blockdev’ didn’t seem to help performance much. SATA seems pretty tuned when compared to hdparm and IDE drives.

After fully tuning it seems we can get about 90MBps out or our disks. Not to shabby. The Linux md driver on RAID 0 didn’t seem to boost IO performance much (and I’m pretty disappointed). Even …

This release of the innotop MySQL and InnoDB monitor is a major upgrade in terms of functionality, code quality, and interface consistency. It is the result of me working for over a month to get innotop into shape for the recent MySQL Conference and Expo. Here’s a summary of the changes: Major changes Quick-filters to easily filter any column in any display Compatibility with MySQL 3.23 through 6.0 Improved error handling when a server is down, permissions denied, etc Use additional SHOW INNODB STATUS information in 5.

The MySQL User’s Conference provides very fertile environment for new ideas. For example, last year we came to the conference with a conviction to build a MySQL agent for our Amanda Enterprise backup and recovery software. However, after talking to many MySQL users about their backup needs we got convinced that stand-alone solution optimized for MySQL DBAs was a better way to go, and that is how Zmanda Recovery Manager for MySQL was conceived.

This year we received a lot of insightful feedback and suggestions from MySQL users and our customers. Special thanks to MySQL engineering and product management for providing their perspective. Here are the major takeaways for us, the MySQL backup guys:

• Back up the MySQL server configuration files when you do backup of the database — that will simplify …

I just got off the phone with Carl Skelton from Polytechnic University and we have finalized the dates for the next camp. MySQL Camp II will be held on Thursday and Friday, August 23-24, in Brooklyn, New York. Polytechnic University has graciously offered to host the camp. More details to follow about the new camp website, places to stay around Polytechnic, and much more. But I wanted to give everyone a heads up. If MySQL Camp II is anything like MySQL Camp I, I expect it to be a breeding ground for new hacks, ideas, and of course, beer.

Connector/Net's MySqlDataAdapter class has a method named FillSchema.  This method is intended to populate the metadata for a given query without actually returning any of the data from the query.  The only syntax that MySQL has to help with this is SQL_SELECT_LIMIT which limits the number of rows that are returned for a given select.  Indeed this is what we are using to prevent the transfer of data across the wire when we only want the metadata.

However, there is a problem.  SQL_SELECT_LIMIT does not work in stored procedures and also does not affect inserts, updates, or deletes.  So, the upshot of this is that calling FillSchema on a stored procedure will, in fact, execute the stored procedure and return all of the data to the client.  This is a waste of bandwidth but it's worse than that.  It will also execute all other DML statements in the procedure.

This is different than what happens with …