The second public alpha version (1.0.14-alpha) of HoneyMonitor Audit Pro - the Edition of the HoneySoftware’s GUI for MySQL™ mainly oriented to Server Administration, Monitoring and Tuning - will be released soon.

In this article I’ll try to describe the new features implemented and the most important bugs fix of this version.

You will find the complete list of bugs fix and improvements in a next post - when we will release v.1.0.14-alpha - and in the Release Notes File included in the build.

Your questions, enhancement requests and comments are welcome.

Contents:

A. New Features

1. Audit System
1.0. Introduction
1.1. Replication
1.1.1. STMT - New connection Option
1.2. Support for the Maria Engine
1.3. Other bugs fix

2. Performance Reports
2.0. Introduction
2.1. Custom Reports
2.2. Report Templates

3. Other …

How dramatic a topic. Anyways, I just send of an email to the PDO list, where I CC'ed a long list of developers from the community and RDBMS vendors. I hope that this will become the starting point for work on a PDO version 1.1. This will hopefully will just be the first step towards even bigger things to come, but lets not get ahead of ourselves. I really think that today we have more developers and vendors interested than ever. Now we just need to figure out how to work together within the PHP development and legal model. But recent discussions, especially with various vendors, have made me more hopeful than ever that we have a chance to make it happen. Please join the discussion if you are interested.

That being said, I wanted to make a few additional points. Who did I include or know about: I contacted Ulf from Sun. …

How dramatic a topic. Anyways, I just send of an email to the PDO list, where I CC'ed a long list of developers from the community and RDBMS vendors. I hope that this will become the starting point for work on a PDO version 1.1. This will hopefully will just be the first step towards even bigger things to come, but lets not get ahead of ourselves. I really think that today we have more developers and vendors interested than ever. Now we just need to figure out how to work together within the PHP development and legal model. But recent discussions, especially with various vendors, have made me more hopeful than ever that we have a chance to make it happen. Please join the discussion if you are interested.

That being said, I wanted to make a few additional points. Who did I include or know about: I contacted Ulf from Sun. …

Though the event is still happening in Charlottesville, VA Nov. 14-16th (Fri night through Sunday), the new web page for OpenSQL Camp is http://www.opensqlcamp.org. The content has been ported over to MediaWiki, and a captcha has been put in place that is activated on any page change that adds an external URL.

Whether you are into MySQL, PostgreSQL, Drizzle, or some other open source SQL database, go forth and register for OpenSQL Camp, without having to login! (Disclosure: if you do not create a login, your IP is tracked.)

One should use timestamps rather than datetimes as timestamps are four bytes and datetimes are eight bytes, right?  This makes sense as smaller indexes and tables are faster than larger ones. However, when I was trying to quantify the improvement (I’m strange that way), I found the exact opposite - when used as a criteria, a timestamp is slower than a datetime. Often much slower.

For example, for this simple sql, when purchaseDate was a timestamp, the query took about 9.4 seconds and the datetime version took about 4.3 seconds. In this case the data was in memory.

    select sum(unit) from Sale where purchaseDate >= '2001-07-01' and purchaseDate < '2001-08-01'

I did other tests, such as when data wasn’t cached and there was io, and I found cases where datetimes were much faster than timestamps, differences so extreme I’m hesitant to report them until I have a better explanation of what is …

I had a hard time coming up with a title for this blog post. I really wanted to capture its essence. Several discarded titles include, but are not limited to:

• How It Works
• The Gory Details
• Everything You Never Wanted to Know
• The Insider's Perspective

I picked the lamest one, hoping that it is catchy enough to ensnare the unfortunate soul that comes across my blog. Just in case you don't know by now, I work for MySQL (ok, Sun) on the Enterprise Tools team. We're approaching (some sort of) release of MySQL Enterprise Monitor 2.0, with the headline feature Query Analysis.

What I want to achieve with this article is to give definitions, data, flow, etc., that describe how we look at things internally in the architecture of the application. This is intended to give the hapless reader an idea of what Query Analysis can do, and consequently what it can not.
…

The Malta MySQL User Group (MMUG) met for the second time this Thursday, and compared to last time, we had a much better venue: Ixaris Systems let us use their board room, so we had all the tools we needed to have a good meeting.

We managed to get a group picture before everyone has arrived, so I guess we can call the people in this picture “early birds”.

Once we all arrived, however, Sandro Gauci from EnableSecurity gave us a very interesting talk on SQL Injection security, and general security flaws from a developer point a view. You can find the slides here: sql-injection.pdf.

Here’s a picture of Mr. Gauci while presenting. (Sorry for the obvious problem with the over-white picture — seems like I …

Are you in Melbourne/VIC, and are you an experienced DBA needing to tune InnoDB? Or do you just maintain some MySQL instances on the side and need to know more about proper installation, security and backup/recovery methods?

Well... the upcoming Open Query course days in Melbourne still have seats available. The topics:

• Monday 15 September: MySQL Installation, Security and User Management (AUD 475 + GST)
  MySQL Server is easily set up and ready to go within mere minutes, however this does not make it suitable for a production environment in terms of performance, security, and monitoring. Additional …

Welcome to the 112th edition of Log Buffer, the weekly review of database blogs.

First, thanks to last issue’s contributors–Joe Izenman, Dan Norris, and Jason Massie–for snatching victory from the jaws of defeat and making LB#111 a worthwhile read. That’s what it’s all about!

Oracle’s up first, starting with our old friend Doug Burns and his Time Matters series, in which he holds up to the light the concept of …

During the process of building the new query analysis feature for MySQL Enterprise Monitor 2.0, we thought the best way to test it at a nascent stage was to use it to tune our own application (since we use MySQL as the backend repository). What we found was actually quite interesting. It also showed that even to seasoned developers, who know that frameworks while helpful, often aren't the most direct, concise way to get things done, can often do very strange things that you don't quite expect.

For those of you that haven't heard about the feature itself, "query analysis" takes all queries that are being processed by a MySQL server, normalizes them into something similar to a prepared statement form by removing literals, and then keeps track of total, min/max, average execution times, result set sizes, etc. at an aggregate …