The MySQL developer tools team announces the next release of it’s flagship product, MySQL Workbench – version 5.2.33. This is a maintenance release only which corrects some problems we didn’t cover in last release. It contains fixes for 7 bugs or enhancement requests.

As always, we want to thank everyone for the great feedback we have received. This helps us to continuously improve the functionality and stability of MySQL Workbench – we appreciate all your ideas for improving MySQL Workbench.  Please keep sending us your ideas!

MySQL Workbench 5.2 GA

• Data Modeling
• Query (replaces the old MySQL Query Browser)
• Administration (replaces the old MySQL Administrator)

Please get your copy from our Download site. Sources and binary packages are available for several platforms, including Windows, Mac OS X and Linux.

…

Digia gets Qt. VMware makes waves. Rackspace launches OpenStack support. And more.

Follow 451 CAOS Links live @caostheory on Twitter and Identi.ca, and daily at Paper.li/caostheory
“Tracking the open source news wires, so you don’t have to.”

# Digia signed an agreement with Nokia to acquire the Qt commercial licensing and services business.

# VMware’s Springsource division acquired Wavemaker.

# Rackspace formally launched services and support for OpenStack via Rackspace Cloud Builders.

# Red Hat defended …

We’re proud to announce the next release of MySQL Workbench, version 5.2.32. This is a maintenance release featuring
a new and improved UI appearance and several corrections and other enhancements.

The tabbed interface has been refreshed to obtain a clearer separation between different modules of Workbench, while improving responsiveness when switching between tabs. The Query Formatter has been rewritten and is now faster and more robust on its handling of queries. The layout of the Administration module has been changed to allow for easier future expansion and use less vertical screen space. Parts that had problems managing MySQL 5.5 servers have been fixed along other total of 53 bugs or enhancement requests have been addressed.

As always, we want to thank everyone for the great feedback we have received. This helps us to continuously improve the functionality and stability of MySQL Workbench – we appreciate all your …

Recently I had to test MySQL Workbench against fresh version of the server. Naturally, the default mysql-server was already installed from repository of my Linux distro. So I installed the latest server version into my /opt/server directory. And then I had several points to resolve, for example, how to start detached server process from Workbench Adminstrator; how to detect if the server is running or not, given that there are many of them running; how to stop the server.

Now I will show several workarounds to perform tasks listed in the previous paragraph. Below are the commands I put into Server Instance Editor, there are corresponding text entries labeled: ‘Start MySQL’, ‘Stop MySQL’, ‘Check MySQL Status’:

- Staring server – (nohup /opt/server/5.5.9/bin/mysql_safe –defaults-file=/opt/server/5.5.9/my.cnf & disown %1)
Note! the command above must be used including parentheses
- …

Hi Folks,

Now that we’re blogging again I thought I might as well continue to do so.

Today we’re reading data from MongoDB with Pentaho Data Integration.  We haven’t had a lot of requests for MongoDB support so there is no step to read from it yet.  However, it is surprisingly simple to do with the “User Defined Java Class” step.

For the following sample to work you need to be on a recent 4.2.0-M1 build.  Get it from here.

Then download mongo-2.4.jar and put it in the libext/ folder of your PDI/Kettle distribution.

Then you can read from a collection with the following “User Defined Java Class” code:

import java.math.*;
import java.util.*;
import …

The attached storage used by Amazon’s managed Relational Database Service has a known issue where the bytes per inode ratio is very high (default on RHEL5 systems is 4096, to be found in /etc/mke2fs.conf). Amazon does not allow any administrative access to these instances so there is no way to reformat the filesystem to allocate more inodes, or attach storage the user can format with a different ratio.

This becomes problematic for databases that have many small tables (generally MyISAM tables, or InnoDB with the innodb_file_per_table setting) which quickly consume the available inodes. When the inode allocation is exhausted MySQL responds with

"ERROR 1030 (HY000): Got error 28 from storage engine"

The only current solution is to increase the size of attached storage, which increases the number of inodes (at the same …

One of our senior MySQL DBAs, Mike Hamrick, wasn’t feeling well this week and so stayed home from the office.  Instead of actually resting, produced this video about reading top output!  I leave it to you all to watch and learn from our local tool tip pro.

And, feel better Mike!

Related posts:

1. Introducing the Bluegecko MySQL Training AMI
2. OurSQL Episode 32: Backup tools you already have [Backup series #2]
3. Ignite MySQL at the MySQL Conference and Expo …

The config files that come with MySQL server are generally not that good. They almost never work well for enterprise server loads and will leave most people wondering why the database needs someone to come fix it. In fact that might be why they roll those configs by default, to keep the consulting services alive and profitable. Personally I have no issues with consulting services, but everyone should start out with good configs to begin with. Well, no worries… here are config files for different system RAM configurations. Just choose the one that fits how much RAM your server has and make sure the cnf file is in place before you install the MySQL server RPM/tar/deb packages. Obviously you’ll want to remove the extension of the filename so it reads “my.cnf” and not “my.cnf_64GB” or the like. These cnfs have default settings in the comments so you know what is changed. There are also several equations listed so you know why I am choosing …

This is the first part of many posts in a series of blog posts where I want to document how the MepSQL packages were built. By doing that, I will also end up covering the MariaDB build system (which this is based on), some of BuildBot, Amazon EC2 cloud and packaging DEBs and RPMs just in general, so it could be interesting from many perspectives. In this first part I'll simply scribble some notes about reviewing the OpenSuse Build System, Launchpad PPA service vs using your own servers and automating the builds with BuildBot.

Originally I just wanted to work on some new ideas on the automated build and QA system used by MariaDB. But since leaving Monty Program I didn't have access to any of those servers anymore, so as a first step I had to look into what alternatives there are for building binary packages for many …

After another week of hacking on MepSQL the DEB files for Ubuntu are now available.(MepSQL is my new "just a hobby" MySQL fork project.)

The Download page has instructions on how to install the packages with a simple apt-get install command. Debian packages will appear soon as they are now easy to add - I mostly just need to add new Amazon images for each.

read more