If you read the comments on this blog, you’ll already know this…

Mark Leith, a Senior Support Engineer at MySQL, sent a link to a talk he gave (at a MySQL users conference) about MySQL for Oracle DBAs. It’s very informative, and I wish I had read it a long time ago. (I also wish I could have attended the talk!)

http://www.markleith.co.uk/dl/MySQL_for_Oracle_DBAs.pdf

He also points out that MySQL has prepared some training “boot camps” for Oracle DBAs about MySQL. I actually knew about this - I signed up right away! I’ll post about it after I take the class (Aug 16).

Thanks Mark!

Not long ago I returned from Mobile Monday Melbourne, and this month I got to see Manny Christophidis from Streamezzo give a talk about what they do. Being my first Mobile Monday event, I had a great amount of fun and learning, and found out that many used MySQL in their work, sometimes passively without even knowing what database sat below them.

Surprised I was, to learn that this event had been going on for nearly two years. If you’re not in the mobile space, you tend to miss out on this not-very-well advertised event, I guess. Seeing as there are more mobile phones being sold these days than personal computers, I think this space is going to get even larger in time to come.

Back to Streamezzo. They make mobile clients, that are really lightweight (100kb Java, and about 200kb Symbian), that …

One of the simplest performance and load tests that can be performed on any web server is to measure the response time of a static HTTP GET request. If you measure how this response time degrades as more parallel connections issue the same request, you can get a basic understanding of the performance and scalability of a web server.

Anyone who's worked with Apache long enough is probably familiar with ab, the  load generator/benchmarking tool which is so wide-spread. This is a sad state of affairs as 'ab' is extremely flawed. I don't want to repeat it's flaws here, as Scott Oaks has done an excellent job of summarizing them. 

Another tool that is also popular is http_load, …

One of the simplest performance and load tests that can be performed on any web server is to measure the response time of a static HTTP GET request. If you measure how this response time degrades as more parallel connections issue the same request, you can get a basic understanding of the performance and scalability of a web server.

Anyone who's worked with Apache long enough is probably familiar with ab, the  load generator/benchmarking tool which is so wide-spread. This is a sad state of affairs as 'ab' is extremely flawed. I don't want to repeat it's flaws here, as Scott Oaks has done an excellent job of summarizing them. 

Another tool that is also popular is http_load, …

In a previous post I described how you could create XML output from SQL using stored functions. But that was a flat structure, with only one table and simple XML structure with a tag for every row in the result set, and column values as attributes or sub tags. Part of the real power of the XML format is that it supports more complicated structures, with hierarchical data. If you need to produce XML for integration with another application you will probably have to produce a XML with data from several tables, and a hierarchical structure. To accomplish this in MySQL we can use the GROUP_CONCAT function, combined with our XML stored functions.

An example:
We take our select statement from the previous post, that gives us a list of tables in xml format:

select xml_tag('table',null, concat(xml_attr('name',t.table_name),
xml_attr('engine',t.engine)),null)
from information_schema.tables t
where …

While it would seem that using Mugshot is for core Linux geeks (it runs on Windows too, you know), I’ve not seen much adoption of the MySQL Mugshot Group, that was announced back in February. I’ve always enjoyed getting the Mugshot client running on my desktop informing me of new RSS feeds in Planet MySQL, so I can read new blog entries relatively quickly.

A new notification method has come upon us - its Twitter. When all is hunky dory, you get IMs or SMSes the moment a post is made from someone you’re following. So I give you the Twitter Planet …

JasperSoft Corporation and MySQL AB today announced the general availability of Jasper for MySQL: OEM Edition 2.0. This updated offering provides significant new features for easier integration and customization, targeted to software ISVs and OEMs seeking an interactive reporting solution to embed in their own MySQL-based products.

Since writing the mmMySQL macro a few weeks ago I have been looking for a way to produce impressive Graphs that would compliment the textual output from the macro.

Creating good looking Graphs often means resorting to Matplotlib in Python, GD in Perl/PHP or RRDTool. The result of these tools is often a static image depicting an historical view of your data, something that does not lend well to a non-daemonized Wiki page. That got me thinking…..how could I embed a graph into the webpage and collect data at the same time?…..a Java Applet!

After a quick search for a …

If you’d take a look at any web site, you will notice, that almost all of the pages on this given site are pretty static in their nature. Or course, this site could have some dynamic elements like login field or link in the header, some customized menu elements and some other things… But entire page could be considered static in many cases.

When I started thinking about my sites from this point of view, I understood, how great it would be to be able to cache entire page somewhere (in memcache for example) and be able to send it to the user without any requests to my applications, which are pretty slow (comparing to memcache ) in content generation. Then I came up with a pretty simple and really powerful idea I’ll describe in this article. An idea of caching entire pages of the site and using my application only to generate small partials of the page. This idea allows me to handle hundreds of queries with one server running pretty slow …

MySQL Slave Delay implements an oft-requested replication feature: the ability to make a slave lag its master, a.k.a scheduling binlog events for some time in the future. This will probably be built into MySQL replication someday, but in the meantime, you can use this tool. A delayed slave is great if disaster strikes and propagates through replication, because it lets you stop the delayed slave before it gets corrupted, restart the slave until just before the offending statement, and recover quickly. This is a lot faster than restoring last night's full backup and replaying a day's worth of binary logs on the master.