Overview

First off, the important news. Tungsten Replicator 2.1.0 was released today.
You can download it and give it a try right now.

Second, I would say that I am quite surprised at how much we have done in this release. The previous release (2.0.7) was in February, which is just a few months ago, and yet it looks like ages when I see the list of improvements, new features and bug fixes in the Release Notes. I did not realized it until I ran my last batch of checks to test the upgrade from the previous release, which I hadn’t run for quite a long time. It’s …

Join us at the next MySQL & Cloud Database Solutions Day hosted by SkySQL & MariaDB in Berlin on June 18th

It’s a beautiful day in Berlin today and we’re putting the final touches to next week’s MySQL & Cloud Database Solutions Day, which takes place on Tuesday June 18th in the facilities provided by Bitkom in Berlin Mitte.

read more

Join us at the next MySQL & Cloud Database Solutions Day hosted by SkySQL & MariaDB in Berlin on June 18th

It’s a beautiful day in Berlin today and we’re putting the final touches to next week’s MySQL & Cloud Database Solutions Day, which takes place on Tuesday June 18th in the facilities provided by Bitkom in Berlin Mitte.

read more

Annnd all set! Check out the recording for the topics below:

Hello everyone!

We missed out on the last meeting time for #DBHangOps due to some conflicts, but we’re looking to come back strong this Wednesday, June 12th 2013 at 12:00pm pacific (19:00 GMT). Come join the discussion and contribute your experience on:

• Upgrading to MySQL 5.6
  • Any issues or gotchas?
• MySQL Python Utilities
  • How do you use them?
• MySQL patches
  • Patches you use
  • Patches you want
• Interesting or valuable Linux kernel settings

Be sure to check out the #DBHangops twitter search, the DBHangops Twitter …

I got a question a while ago that I thought was quite simple, but turned into an interesting discussion: How much hard disk space does a database take up?

As it happens, there's a simple answer and a much, much more involved (yet ill-defined) answer, and which one you choose depends on what you think goes into a database and how very, very pedantic you are.

The Simple Answer

You can query the size of table and index data using Information Schema or SHOW TABLE STATUS. The columns DATA_LENGTH and INDEX_LENGTH contain the number of bytes for the table and index data respectively. You can construct simple queries based on that data, or do a quick search on the web for more interesting queries (For example, Peter Zaitsev of Percona wrote a post …

Here’s the recording!

Heyo!

Now that we’ve gone through the Percona Live MySQL Conference and Expo review and had an amazing turnout to talk about it, it’s time to open up the discussion around things that DBAs want to talk about and need to be conscientious of. Join us on Wednesday at 12:00pm PDT (19:00 GMT) to take part in the discussion and share your knowledge and experience with the following topics:

• Filesystems and MySQL — Which do you use and why?
  • Do you handle I/O alignment? How do you do it?
  • Scheduler changes?
• Nagios checks! — Any new checks you’ve added recently?
• The worst settings in MySQL that you always change
• What are the most important variables to you, and what do you set them to?
• What will be important variables in 5.6 that …

Original images from Flickr user jenniferwilliams

One of our clients, for various historical reasons, runs both MySQL and PostgreSQL to support their website. Information for user login lives in one database, but their customer activity lives in the other. The eventual plan is to consolidate these databases, but thus far, other concerns have been more pressing. So when they needed a report combining user account information and customer activity, the involvement of two separate databases became a significant complicating factor.

In similar situations in the past, using earlier versions of PostgreSQL, we've written scripts to pull data from MySQL and dump it into PostgreSQL. This works well enough, but we've updated …

MySQL Sandbox has been updated again. The latest version is 3.0.38, which was just released. There were four releases in the space of one week, and this last one is just a polished edition.

Cherry-picking from the Change log:

• Added option --bind_address to complement the effects of --remote_access;
• The script 'enable_gtid' (for MySQL 5.6 +) now is durable. Previously the changes did not survive a restart.
• Now you can install MariaDB with its bizarre version '10.0'
• It also works well with MySQL 5.7. A bug prevented the creation of 'enable_gtid', but it …

MySQL Enterprise Backup (MEB) was born 3 years ago as a newly branded avatar of InnoDB Hot backup. Wanted to share what has gone on so far, how we at Oracle think about

backup, the milestones that we have achieved and the road ahead. The idea for this blog came to me after looking at Mikael's latest blog. While Mikael talks about MySQL, I want to talk about MEB.

When we started with InnoDB Hot backup the first challenge was to have it adhere to the development, quality and release processes for MySQL. This meant creating a

quality plan, getting it into the development trees of MySQL and ensuring that each piece of new code went through architecture and code review. Though the initial implementer and architect of Hot backup continues to work with the MEB team, there were a host of new engineers to be trained. We also …

SAP HANA , having entered the data 2.0/3.0 space at the right time, has been getting traction lately; and there will be lot of users like me who wants to[...]