We are pleased to announce the release 1.0.16 of HoneyMonitor, our GUI for MySQL™ administration and monitoring.

In this release, available for immediate download, we have fixed many bugs and included several improvements.

We are working to release a RC version as soon as possible.

The following is the list of changes:

• New Features:
  • new Tab “Defaults Folders” in the “HoneyMonitor Options” Window to set the default folders to be used when storing Audit Reports, Standard Reports, HTML Reports, Queries, Backups, Scripts, Exported Data.
• Improvements:
  • during the installation of the Audit System, it is now possible to choose the engine of the Audit Table. InnoDB is used by default.
  • when connecting to a server through Network or Audit Pro Editions, now a message alerts users if Event Scheduler is stopped.
  • minor improvements to the Filter Editor: an info-icon has been included to help users when setting a filter condition.
  • a different structure of directories is now used to store users’ files created through HoneyMonitor (queries, reports, backups). All the files are now stored as default in the folder Documents\HoneySoftware\HoneyMonitor.
  • minor improvements in the Binary and Relay Log Editor.
  • improved stability of Connections to MySQL™: both for direct and SSH Tunneling connections.
  • several improvements in the “Connection Window”:
    • it is now possible to specify a SSH Key for Tunneling Connections;
    • it is not mandatory anymore to set a local port number for SSH Tunneling Connections: you can set it or leave the default 0 value. If 0 is chosed a random (free) port will be choosed by HoneyMonitor;
    • it is now possible to store a connection even if it fails (a new “Save and Close” button has been added in the “Connection Window”, when the Window is in “creation mode”). Prior to this, it was possible to edit a connection but it was not possible to create a stored connection if that connection was failing.
    • it is now possible to edit a stored connection at software startup (before, it was possible only to select a stored connection or create a new one, and it was possible to edit a stored connection only after “entering” in the software - e.g. after “Server Objects List” was loaded.
  • several improvements to the “Unable to Connect” Window: added more information and tips to better indetify and solve occurred connection errors.
  • minor improvements in the Performance Tuning Monitor: now the Report Preview is opened in a new Window, outside the Monitor, for a better usability.
  • several other minor improvements.
• Bugs Fix:
  • some Editors were closed even if not able to save, after choosing “yes” on the message “Would you like to save your changes?”.
  • due to a wrong Edition limitation, in the Audit Pro Edition of HoneyMonitor, it was not possible to open the Report Preview using the top menu included in the software. Now fixed.
  • Plugin Editor: Editor was opening a different plugin (the first) than that selected in the “Server Objects Lists”.
  • fixed several inconsistencies between the active node of the Server Objects List, the software captionbar and some top level menus: now, if a connection is closed, many menus are disabled so users can’t open some Windows or Editors until they connect to a MySQL™ Server using the Server Objects List or the “Connect” menu entry.
  • many Wizards now remember the last used directory for storing files (backups, HTML reports, reports, …).
  • if any error occurs when executing FLUSH or RESET queries (feature called from the top menu of the software), now the message that is shown is formatted in a better way.
  • changed some red lines with blu and orange ones. Red color is typically associated to “alert status” so we have changed it for better intuitiveness. Green and red colors are now used as symptom of “no attention needed” and “attention needed”. Blue and orange lines are just graphical elements and are not associated with alert status at all.
  • better error handling when connecting on a server using a wrong STMT statement.
  • better error messages when pinging and shutdowning the server (if any error is returned).
  • several bugs fix in the Trigger Editor.
  • several bugs fix in User’s Privileges Window.
  • several bugs fix in User Editor.
  • several bugs fix when saving a script file from the Script Editor.
  • several bugs fix in the actions performed through the popup menu of the Plugins Tab of the Server Properties Window.
  • several bugs have been fixed in the Connection Window:
    • sometimes, when testing SSH Tunnels, Connection Window was saying that local port for SSH Tunnel was in use even if it was not.
    • when editing a stored connection, changes made in the local port number used for SSH Tunnel were not saved, if other options were not changed at the same time.
  • several bug fix in HoneyMonitor Options Window (when using this window with no MySQL™ connections opened, some errors were occurring).
  • several bug fix in Editor Options Window.
  • several bugs fix when attempting to reconnect: there where some bugs when, after software lost connection to the server, it was automatically trying to re-establish the connection. Now software should reconnect silentely (in a transparent way from a user point a view).
  • several bugs fix in the Federated Server Editor:
    • even if set, socket option was not included in the query when creating a Federated Server (it was working fine when the Editor was in “editing mode”);
  • several bugs fix in the HTML Report Wizard.
  • several bugs fix in LogFile Group Editor.
  • several bugs fix in TableSpace Editor.
  • several bugs fix in the Routine Editor:
    • some errors where occurring while opening the Editor with limited-privileges users;
    • parameters’ popup menus were not localized in English.
  • several bugs fix in the UDF Editor: under some conditions, a wrong DROP FUNCTION query was executed while adding a new UDF function.
  • several bugs fix in the Server Properties Window:
    • bugs fix when changing values of the variables “general_log_file” and “slow_log_file” on Windows™.
  • several bugs fix in the Metadata Catalog:
    • bugs fix when connected over MySQL™ version 6.x (MySQL™ Bug #33106).
  • minor bugs fix in the localization of the Replication Monitor.
  • minor bugs fix in Server Object List.
  • minor bugs fix in Log Management Window.
  • minor bugs fix in the Performance Tuning Monitor.
  • minor bugs fix in the Field Editor when used for Timestamp fields in MySQL™ 6.
  • minor bugs fix in the Table Editor.
  • minor bugs fix in the string “username@hostname:port” shown in the captionbar of the software: now the output of the query “SELECT CURRENT_USER();” is used.
  • minor bugs fix in the Backup Wizard.
  • minor bugs fix in the style of the Calendar controls used in some Windows (minor compatibility issues with Systems with English local Settings).
  • minor bugs fix in the Audit Reports: a better font size is now used for report head.
  • several other minor bugs fix.
• Other:
  • compatibility tests with MySQL™ ver. 5.1.31, 5.1.32, 6.0.9-alpha and 6.0.10-alpha.

Beginning with version 1.0.16, we have started some tests to ensure the compatibility of our software with Windows™ 7 - the new Microsoft™ Operating System, now in beta.

Here’s some screenshots on how HoneyMonitor looks in Windows™ 7:

Playing with MySQL™ Cluster Replication	Performance Tuning Monitor	Audit Report Preview
View Editor - Query Builder	Playing with MySQL™ Logs and Server Properties	Show Monitor and some Editors

For more information about HoneyMonitor please visit the product page at http://www.honeysoftware.com/honeymonitor.

Your questions and bug reports are welcome at support at honeysoftware dot com. You can also contact me directly for any requests you might have.

The Beta Program for the HoneyMonitor Project is running and your feedback is much appreciated! Feel free to send us also your enhancement requests and your comments about the features you would like to see in next versions of our software!

I will be at FOSDEM - Free and Open Source Software Developers’ European Meeting - in Brussels, tomorrow Saturday 02/07 and the day after.

This year MySQL™ has a Project Stand and a Developer Room, with many interesting talks scheduled.

For me, that’s a nice occasion to meet the European part of the MySQL™ Community Team as well as other SUN™ employees and developers.

Here’s a Google map of my way to Brussels:

View Larger Map

See you at the SUN™ OpenSolaris™ / MySQL™ Stand!

I was looking for some info on liveblogging art this am because I never did a similar activity and was wondering if I am able to do it in the next confs I’m gonna taking.

Liveblogging means taking notes about a conference session you are listening and share the main concepts of the talk with people who are not present in the room.

I’ve found some tips on how to start a successful liveblogging session and tested a cool platform: http://www.coveritlive.com.

You know, liveblogging at a conference is very important for people who can’t attend it. It helps, among with pics and videos, to smell the great atmosphere you can breathe in a community event.

I think things are evolving well from this side.

If I am not mistaken, the most easy way to liveblogging is to create a short blog post during the speech and publish it at the conclusion of the talk. You can search for several mysql-related liveblogging examples on the Planet MySQL™. For instance, there you can find some liveblogging posts created during past editions of the MySQL™ Conference and Expo.

In my search, I’ve found a cool tool that can help guys who wants to liveblog during conferences (are you attending FOSDEM next weekend? eh, eh: why don’t you liveblog?)

In short, what you need is:

• create a free account at http://www.coveritlive.com
• login in that website and create a new liveblogging session
• create a post on your blog and embed the code from your account @ http://www.coveritlive.com
• inform users that they will find your liveblogging in that blog post (you can also send some invitations before the session starts using the coveritlive.com console; also users can subscribe from your blog post and get a reminder message few mins before the start of the presentation).

That’s it!

I did two quick tests: one test of the coveritlive.com console (without a real blog post, just to get familiar with the console itself) and another test with a real blog post in order to simulate a real scenario.

Below you can see two screenshots of the coveritlive.com console (read the text within the images for more info).

 

And here - http://www.honeysoftware.it/sleto/morpheus/2009/02/02/liveblogging-test/ - you can see the final result of test no. 2.

Here the key-word is interaction during the liveblogging. Rather than publish a blog post at the end of the presentation, you publish it the night before thus informing users on the web address where they can see your liveblogging. Furthermore, users not only see in real-time your notes, but can also send comments or questions to you, and thru you, to the speaker.

I’ve two problems with liveblogging, though: the first is the language, since I am not a native English speaker I am not sure I am able to write down speech as fast as it is required. The second is that I don’t have a light laptop but an old heavyweight and the third is that I think the battery of my laptop has just 1 min autonomy.

In a twitter tag: #ThatSWhyIWantToBuyANewDellLaptopASAP ;)

This excursus on liveblogging has been very useful for me.
But what about you? Will you liveblog in the next conference you are going to take?

If yes, have fun with your next liveblogging session!

Some resources:

• How to Live Blog a Conference - http://mashable.com/2008/07/04/live-blog-conference/
• CoverItLive’s Interactive Widget for Bloggers - http://mashable.com/2007/11/26/coveritlive/
• Cover it Live - http://www.coveritlive.com
• Live blogging test - http://www.honeysoftware.it/sleto/morpheus/2009/02/02/liveblogging-test/

We are pleased to announce the release 1.0.15 of HoneyMonitor, our GUI for MySQL™ administration and monitoring.

In this release, available for immediate download, we have fixed some bugs without adding many new features.

We are working to release a RC version as soon as possible.

The following is the list of changes:

- New Features:

1. new menu entry Auditing / Reports / Edit Report’s Template / Custom Report.

- Improvements:

1. minor bugs fix and improvements in the Report Designer.

- Bugs Fix:

1. on Vista™, the Report Designer was losing the connection after opening the report preview. Now fixed.
2. InnoDB Performance Report: an incorrect % simbol was on the chart Innodb_rows_xxx_per_second. Now removed.

3. other minor bugs fix.

- Other:

1. compatibility tests with MySQL™ ver. 5.1.29-rc, 5.1.30, 6.0.7-alpha.

Version 1.0.16 will be released within few weeks.

Recently we also have updated the Reference Manual:

1. English Edition: v.1.0.15 Rev.226
2. Italian Edition:v.1.0.15 Rev.1043

For more information about HoneyMonitor you can visit the product page at http://www.honeysoftware.com/honeymonitor.

Your questions and bug reports are welcomed at support at honeysoftware dot com. You can also contact me directly for any requests you might have.

The Beta Program for the HoneyMonitor Project is running! Feel free to send us your enhancement requests and your comments about the features you would like to see in next versions of our software!

Other posts  you might be interested in:

• Step by Step Guide on How to Create a Customized Performance Report using HoneyMonitor

 
As you probably already know, yesterday the GA version of MySQL™ 5.1 has been released :)

To celebrate this great event, I have organized a little event with some of my friends @ Trieste University, Italy.

Since I am a physics alumn and I still have some friends who study physics, I decided to organize a sort of unofficial “Trieste MySQL™ 5.1 GA Day” to have some funny moments with them at the Physics Department ;)

I am using MySQL™ 5.1 since the third public version (5.1.5-beta, January 2006) and I have installed and tested all the 24 versions from 5.1.5-beta :)

For the occasion, I bought a chocolate pie and a good Italian sweet wine (Ramandolo).

I also bring:

• the Limited Edition ;) “MySQL™ Contributor” polo shirt I won for the position 10 of the MySQL™ Use Case Competition
•  the Sun | MySQL™ bag I received during the latest MySQL™ Central Europe Conference
•  one of the Sakila Dolphins Giuseppe threw to the roman students attending the event organized by the Sun | MySQL™ Italian Team last May, when Marten Mikos came in Italy

The pie dedication I agreed with the confectioner was “Welcome MySQL 5.1 G.A. November 27, 2008″ but I don’t know why ;) he changed “MySQL 5.1 G.A.” in “5.1. G.A. - M.y.S.Q.L.” :-/

Also I gave a good splash of the Dolphin but it seems that he drew a ornithorhynchus rather than a dolphin ;)

BTW, the pie was delicious!

I would like to virtually dedicate this pie to all Developers, Q.A. Engineers, Support Engineers and the other friends @ Sun | MySQL™.

Especially, I would like to cite Miguel Solorzano & Sveta Smirnova @ MySQL™ Bug Tracking and, of course, friends @ Community Team.

Unfortunately, I didn’t have the time to organize a bigger event and invite you to join :( since I am very busy with my work and the MBA in this period. It has been a sort of private event (thanks Luca for the photos and Enrico for placing your car to my disposal) but it has been very fun!

I have uploaded some pics here, enjoy!

Reading this article you will learn how to create a Customized Performance Report for one of your MySQL™ Servers using HoneyMonitor, a GUI for MySQL™ Server Administration, Monitoring & Performance Tuning.

Contents

• Introduction
• Step 1 - Choosing a File Name and Opening the Report Designer
• Step 2 - Editing the SQL Queries used by the Report
• Step 3 - Editing the Charts contained in the Report
  • Axis Name
  • Series
• Step 4 - Other minor changes
• Step 5 - Previewing our Customized Report
• Few Considerations and Useful Tips
  • Actual Date Interval
  • Reopening the Customized Report
  • Getting Ready for the Creation of a new Customized Report: Editing the Customized Report Template
• Other Resources
• Conclusion
• About the Author

Introduction

HoneyMonitor includes about 10 ready-to-use Performance Reports (Temporary Tables, Query Cache, InnoDB, …) which can help you monitoring and tuning your MySQL™ Server.

The total number of Performance Charts included in the Reports is about 90.

With a Customized Report you can choose to monitor a specific variable not included in the standard reports and create a Report that better fits your need. To allow you creating a Customized Performance Report, HoneyMonitor integrates a powerful Report Designer, FastReport™.

In this short Tutorial, we will see how to create a simple Customized Report, which contains one chart on which we can see how a specific performance ratio is changing over time.

In general, you can add many series on the same chart, or many charts in the same report. Procedures explained in this article can easily be extended to more complex cases.

Information included in the article apply to:

1. HoneyMonitor Audit Pro Edition
2. HoneyMonitor Network Edition

Before going on with the reading, please make sure that the version of your MySQL™ Server is 5.1 or higher. For the complete list of MySQL™ versions supported by the Audit System included in HoneyMonitor, please refer to the HoneyMonitor’s Reference Manual.

To simplify the creation of your first customized Report, we have created a Report Template and we have included it in the HoneyMonitor installation. Each time you create a customized Report, the Template will be your starting point; it already includes some standard queries and one chart ready to be modified by you.

After the creation of your first customized Report, in order to speed-up the creation of your next Reports, you can edit the Report Template. We will came back to this point, later, in the last subsection of this article.

Step 1 - Choosing a File Name and Opening the Report Designer

To create a Customized Performance Report, please click on the menu Auditing / Reports / Custom Report (Fig. 1).

Fig. 1: Creating a Customized Performance Report - Step 1 - Image 1.

You will be prompted by a Windows™ Dialog to choose the name and the path of your new Report. Please choose a Filename and click on the “Ok” button of the dialog (Fig. 2).

Fig. 2: Creating a Customized Performance Report - Step 1 - Image 2.

FastReport™ will be opened (Fig. 3).

Fig. 3: Creating a Customized Performance Report - Step 1 - Image 3.

Step 2 - Editing the SQL Queries used by the Report

In the second Step of this guide we would like to edit the SQL Queries which will be used by the Report Designer to generate the (prepared) Report.

Please, click on the “Data” Tab of the Report Designer, and then double-click on the icon “SQL_Query1″. A dialog containing a SQL Query will be opened (Fig. 4).

Fig. 4: Creating a Custom Performance Report - Step 2 - Image 1.

We will edit this query to select the data we would like to include in the Report.

The basic idea is the following: we have an audit table which contains the values of many system and status variables as well as the values of many derived variables (ratios). This audit table is populated by the Audit System included in HoneyMonitor. In our Customized Report, we would like to select one of these variables - or create a new customized ratio - in order to see how it is changing over time.

Let’s do the simpler case and suppose we want monitoring the variable “Inserts_per_Second” (for a list of available columns of the audit table, please goto
http://www.honeysoftware.com/products/honeymonitor/auditpro/available_variables.html).

We can proceed replacing the line


### `hs_audit_schema`.`status_system_dpm_table`.`your_variable_name`,


with the line


` hs_audit_schema`.`status_system_dpm_table`.`Inserts_per_Second`,


(change `Inserts per Second` with the variable your prefer; you can also select other variables if you want to add more series in the chart or you want to add more charts in the Report).

Now we would like to choose a time interval in order to retrieve only the data of a specic period.

Let’s assume we want monitoring the period from ‘2008-10-10 00:00:00′ to ‘2008-11-10 00:00:00′.

Hence we replace the line


WHERE
`hs_audit_schema`.`status_system_dpm_table`.`g_timestamp` > :min_limit
AND
`hs_audit_schema`.`status_system_dpm_table`.`g_timestamp` < :max_limit


with the line


WHERE
`hs_audit_schema`.`status_system_dpm_table`.`g_timestamp`
> '2008-10-10 00:00:00'
AND
`hs_audit_schema`.`status_system_dpm_table`.`g_timestamp`
< '2008-11-10 00:00:00'


The result would be similar to that shown in Fig. 5

Fig. 5: Creating a Customized Performance Report - Step 2 - Image 2.

Let’s now edit the WHERE clause of “SQL_Query2″ as we did for “SQL_Query1″. The result would be similar to that shown in Fig. 6.

Fig. 6: Creating a Customized Performance Report - Step 2 - Image 3.

In general, you don’t need to edit “SQL_Query3″. You can use this query, for example, to retrieve additional information about the server.

The query you will find pre-loaded if you double-click on the “SQL_Query3″ icon is shown in Fig. 7.

Fig. 7: Creating a Customized Performance Report - Step 2 - Image 4.

Step 3 - Editing the Charts contained in the Report

The Template of the Customized Report includes one chart. You can add more charts in the Report selecting the chart you would duplicate and using the standard Copy (CTR+C) and Paste (CTR+V) commands.

In this Step we will see how to include in the chart the variable “Inserts_per_Second” retrieved by the query edited in the last step of this Guide.

Please, click on the “ReportPage” Tab, select the chart and click on the right button of your mouse. A popup menu will be displayed; if you click on the “Edit” entry (Fig. 8) the “Chart Editor” will be opened.

Fig 8: Creating a Customized Performance Report - Step 3 - Image 1.

Axis Name

Firstly, you would change the name of the chart.

To change this property, as well as other properties, you can use the “Property Grid” of the “Chart Editor” (Fig. 9).

Fig. 9: Creating a Customized Performance Report - Step 3 - Image 2.

Please expand the “BottomAxis” item and then scroll down until you see the entry “Title”. Select it and edit the “Caption” Property as shown in Fig. 10 and 11.

Fig. 10: Creating a Customized Performance Report - Step 3 - Image 3.

Fig. 11: Creating a Customized Performance Report - Step 3 - Image 4.

The result would be like that shown in Fig. 12.

Fig. 12: Creating a Customized Performance Report - Step 3 - Image 5.

After editing the chart’s name, make sure to click on another row of the Properties Grid, so that the change will be stored.

Series

Let’s now add a series on the chart.

Please click on the “Fast Line - Series2″ item of the “Chart” Tree and then select the “Insert_per_Second” field from the “Y” combo-box contained in the “Values” frame (Fig. 13).

Fig. 13: Creating a Customized Performance Report - Step 3 - Image 6.

Hence click on the “Ok” button of the “Chart Editor” and save your Report by clicking on the File / Save menu.

Step 4 - Other minor changes

We are almost ready to preview our Customized Report. You probably would edit some labels or do other minor changes in the Report Template.

This is the right moment for such activities (Fig. 14).

Fig. 14: Creating a Customized Performance Report - Step 4 - Image 1.

Step 5 - Previewing our Customized Report

You can now click on the “Preview” button of the Designer toolbar to open the prepared report. If the date interval you have chosen returns records, you will see a line representing the trend of the “Inserts_per_Second” variable in the chosen time interval.

In the example created for this tutorial, that variable has the trend shown in Fig. 15.

Fig. 15: Creating a Customized Performance Report - Step 5 - Image 1.

Once the (prepared) Report has been created, you can print it or export it in PDF.

Note: data used for this tutorial have been created, on a local server, using the following method. I have created a simple application which performed a certain number of Insert queries each second, and then, on alternate days, I switched on and switched off another similar application in order to reproduce a simple stair chart.

Few Considerations and Useful Tips

Actual Date Interval

In our example, we have chosen the interval [’2008-10-10 00:00:00′, ‘2008-11-10 00:00:00′].

In general, we can’t be sure that the audit table contains at least one row for the initial date and one row for the final date. That’s why, in all our Performance Reports, we have included additional information about the date of the first and the last records used by the chart, which in general can be different from those specified in our SQL queries, as you can see from Fig. 16.

Fig. 16: Creating a Customized Performance Report - Date Issue.

Reopening the Customized Report

The next time you want open your Report, to edit it or just to recreate the (prepared) Report for a different period of time, you can use the menu Utility / Edit Report (Designer), Fig. 17.

Fig. 17: Reopening the Report - Image 1.

You can also add a link to the “Server Object List” to have a more elegant way to reopening the Report just created (Fig. 18).

Fig. 18: Reopening the Report - Image 2.

Getting Ready for the Creation of a new Customized Report: Editing the Customized Report Template

The Customized Report Template is your starting point for your Customized Report.
You can edit it, if you want, to speed-up the creation of your next Performance Reports.

To do this, click on the menu Utility / Edit Report (Designer), select the file honeymonitor-
installation-path\audit\reports\custom_report_template.fr3 and edit it as you want (do a backup copy of the original file before start editing).

Other Resources

If you want to learn more on HoneyMonitor please visit the Project Home Page, at http://www.honeysoftware.com/honeymonitor, or check out one of the following resources:

• Getting Started Guide
• Video Tutorials
• User’s Guide

Conclusion

In this article, we have seen how to create a Customized Report for monitoring the performance of a MySQL™ Server using the Audit System and a powerful Report Designer integrated in HoneyMonitor, a GUI for MySQL™ Server Administration, Monitoring & Performance Tuning.

Here’s a list of other posts you might be interested in:

• Performance Monitoring, Tuning & Auditing in MySQL® 5.1 - A GUI Approach - PART 1
• HoneyMonitor v.1.0.14 released!
• HoneyMonitor v.1.0.14-alpha - New Features Preview

About the Author

Santo Leto is a two years experience MySQL™ DBA and Developer.

Leader and main programmer of the HoneyMonitor Project, he graduated in physics from Trieste Univeristy, and he lives in Italy, where he works from home.

I am starting a trip of two days to Munich to attend tomorrow, October 21st 2008, the MySQL™ Central EU Customer Conference.

And.. sure! I am still wondering why I am coming stated that I don’t understand German :-/
I thought that the Conference was in English or at least part of it but.. eh eh eh.. it seems it isn’t.

Two things deceived me. The name “Central Europe” and the possibility to come with some friends which are used to go in Germany in this period to drink liters of beer.

Possibility no. two vanished cause one of them went away to U.S. for a short period @ Standford University and the others are very busy during this week.

Moral:

• devote yourself to Euroregions and EU Political Integration as much as you can, :-0
• start learning German so that the next time you would be prepared to such mishap, and.. of course: English as well ;-)
• press SUN™ to organize a Conference in Italy - I suggested some months ago a Conference entitled “MySQL™ 5.1 GA Day” :-/

BTW, attending a MySQL™ Conference in German is better than non-attending an English Conference (London), especially if your model managers are present ;-)

So, see you tomorrow!

We are pleased to announce the release 1.0.14 of HoneyMonitor, our GUI for MySQL™ administration and monitoring.

With this release, available for immediate download, all HoneyMonitor’s Editions:

• Lite Free
• Standard
• Enterprise
• Network
• Pro
• Audit Pro

reach the beta stage. The following is the list of changes:

• New Features:
  • new Virtual Data Grid for a better management of data in HoneyMonitor (insert / edit / delete of records) [it is linked to the Table Editor, Queries Editor, View Editor, Server Objects List].
  • new menu entry Database Objects / Tables / Open Table’s Data (Quick Way).
  • new menu entry Auditing / Reports / Custom Report. Possibility to create a customized Report using the Audit Table (useful to see how a numeric variable (raw or calculated) is changing over time).
  • new menu entry Auditing / Reports / Edit Report’s Template to edit the Templates of the Performance Reports.
  • new menu entry Utility / Edit Report (Designer).
• Improvements:
  • minor improvements in the Metadata Catalog.
  • minor improvements in the log output created by the Data Transfer.
  • several improvements and bugs fix in the Log Management Window.
  • Server Objects List:
    • support for servers’ groups;
    • minor improvements in the popup menu;
    • new menu entries “Import Link” and “Drop Link” in the popup menu of the Queries, Reports, Backups nodes;
    • new toolbar button to refresh all opened connections.
  • minor improvements to Audit Statistic Window:
    • a “Refresh” button has been added;
    • 3 new fields now show the date of the first and last audit record included in the audit table and the date difference.
  • you can now open more than one instance of the User’s Account Manager.
  • improvements in the administration of the FALCON variables.
  • minor improvements in the Report Connection Choice Window.
  • new NetStat Window to see if a local port is already used before opening a SSH tunneling connection.
  • Connection Window: new STMT option (very useful, for example to set SET SQL_LOG_BIN = 0).
• Bugs Fix:
  • bugs fix in the LogFile Group Editor.
  • Field Editor (TIMESTAMP default value).
  • minor bugs fix in the Routine Editor (parameters).
  • minor bugs fix when changing software language.
  • minor bugs fix in the Performance Tuning Monitor.
  • minor bugs fix in the Change Master Wizard.
  • bugs fix when installing the Audit Database in a Master / Slave environment: SET SQL_LOG_BIN = 0 is now used, so you don’t need to filter replication anymore.
  • minor bugs fix in the Replication Monitor.
  • bugs fix when establishing a SSH tunneling connection (Table Editor, View Editor, Queries Window).
• Other:
  • audit system: compatibility with MySQL™ 6.0.6-alpha:
    • support for the Maria Engine in v.6.x;
    • status variables Com_show_column_types and Innodb_buffer_pool_pages_latched have been deprecated (MySQL™ Bugs #36793 and #5299).

One of the most important feature included in this version is the new Virtual Data Grid that allows you to retrieve and edit your data (insert / update / delete).

Thank to the vitual system, you can open very big recordsets.

Below you find some screenshots. We will try to update the documentation and add more video tutorials as soon as possible.

For more information about HoneyMonitor you can visit the product page at http://www.honeysoftware.com/honeymonitor.

Your questions and bug reports are welcomed at support at honeysoftware dot com. You can also contact me directly.

Other posts  you might be interested in:

• HoneyMonitor v.1.0.14-alpha - New Features Preview

Dear Kaj, Giuseppe, Jay, Lenz, Colin,
MySQL™ Community Team,

This is my Report for the MySQL™ 5.1 Use Case Competition.

Before start reporting on my use of the new 5.1 Features, just a note.

I was quite sure on early August 2008 that including similar posts in my Report would be allowed. But during an email conversation, Giuseppe told me that similar Reports won’t qualify for the competition because the Community Team was looking for Reports on ‘Real Word’ usage of MySQL™ 5.1 in production systems rather than a description of software specific features though implemented on MySQL™ 5.1 features.

BTW, I decided to go on with my series of articles as I wrote in this post (I published it only today, before it was just a draft).

Nevertheless, few weeks ago, after reading this post by Lenz I changed my mind once again about the real stuff a UC Report should contain and today I think that my Report could be admitted (if that has been admitted).

So here’s my report ;-)

http://www.honeysoftware.it/sleto/blog/ucc/sleto-MySQL-5.1-Use-Case-Reports.pdf

Username and password has been sent to the Community email address.

Enjoy!

My last post Using Partitioning in MySQL™ 5.1 would be the last post of the Series “Using Feature XXX in MySQL™ 5.1″.

I started write this series of articles on August 2008 when I heard about the MySQL™ 5.1 Use Case Competition and decided to let the Community Team of MySQL™ know about what I’ve developed and included in HoneyMonitor, the HoneySoftware’s GUI for MySQL™.

I’ll comment about the 5.1 UCC later on a new post.

Here’s the links of the articles included in the series:

1. Using Partitioning in MySQL™ 5.1
2. Using Table Log in MySQL™ 5.1
3. Using Cluster Disk Data in MySQL™ 5.1
4. Using Plugins in MySQL™ 5.1
5. Using Federated Servers in MySQL™ 5.1
6. Using Scheduled Events in MySQL™ 5.1

I’m sure this articles won’t be useful for guru or users who, like me, are using v. 5.1 since early versions: probably all of them know pretty well new features of MySQL™ 5.1. On the contrary I hope that this articles could be useful for newbies or for users of the version 5.0 (or 4.1) who were not aware of the amazing new features included in v. 5.1 (or for users who are thinking to upgrade).

Of course, all new features are described in those articles from my prospective (that is a GUI prospective).

If you are not sure about upgrading your Database Server to v.5.1 the following (partial) list of articles could help you taking your decision, too:

• Why you want to switch to MySQL 5.1 (Sheeri Cabral)
• Choosing MySQL 5.1 over 5.0 (Ronald Bradford)

Please, feel free to add a comment with the links to your articles. The above list refers just to the articles I can mind at this moment.

Now that this series is completed, by the end of the year I’ll try to write the second and third parts of the series “Performance Monitoring, Tuning & Auditing in MySQL™ 5.1 - A GUI Approach”.