Just in case you don't know resizing Innodb log file is not just simple as changing the value of innodb_log_file_size in the MySQL configuration file. But its even more simpler. Follow the steps in this post and you will be done with the resizing.

The open-source xtrabackup tool from Percona brings much needed hot backup functionality to MySQL deployments.  In this database journal article we discuss logical, cold, and hot backups, then explain how to use xtrabackup on your MyISAM, InnoDB, and XtraDB tables to create at-the-ready backups.  We then take you through the step-by-step process to restore them, and even the process of point-in-time recovery too.

Database Journal – Hotbackups with Percona’s Xtrabackup

I am happy to announce that MariaDB 5.2.3 is now released as a stable release.

During the gamma period we did not receive any serious reports for issues in 5.2, so we are relatively confident that the new code is of decent quality.

You can read about the features of MariaDB 5.2 in my previous blog entry or in the fast growing MariaDB knowledgebase..

What is most interesting about MariaDB 5.2 is that most of the features came from the MariaDB/MySQL community, not from Monty Program Ab!

Without the community it would not have been possible to do a stable release so soon after the last release. Virtual columns, …

Although MyISAM has been the default storage engine for MySQL but its soon going to change with the release of MySQL server 5.5. Not only that, more and more people are shifting over to the Innodb storage engine and the reasons for that is the tremendous benefits, not only in terms of performance, concurrency, ACID-transactions, foreign key constraints, but also because of the way it helps out the DBA with hot-backups support, automatic crash recovery and avoiding data inconsistencies which can prove to be a pain with MyISAM. In this article I try to hammer out the reasons why you should move on to using Innodb instead of MyISAM.

It's soon time to celebrate 30 years of IBM PCs (They were first released in 1981, initially in the US and Canada). Before that, the microcomputer maket was much more diversified, but once IBM released the PC, most of what remained, after a few years, was the PC itself and Apple.

If you remember how it all started though, with the MITS Altair kits, you might also recall the biggest competitor to MITS, IMSAI. IMSAI, big as they were, died off by the early 1980's.

So then, what about the title of this blog? What the heck is ComputerLand? And amusement park? Nope, far from it. Actually, if you were in the US in 1981 and decided you wanted to buy a PC, you had few options of where to get one. Either one of the few Sears stores that had them, but those were very few, or ComputerLand. That was about it, for a while. And ComputerLand was big, real big! And they started growing even bigger, having something that was close to a …

Just a small announcement:

Starting today, I am now “MySQL Database Architect” at Twitter, where I am joining some old friends on the small but hard-working DBA and operations teams there. I’ll be working to help debug, support, and scale the MySQL databases, of course, and who knows what else. I’m looking forward to the challenges and fast paced operations again. I’m also looking forward to writing a lot more on this blog about MySQL. I’ve had a Twitter account for a long time, but I suppose I’ll write a lot more on it now:

Since I will now be commuting from Sunnyvale to San Francisco nearly daily, …

It's finally official — please join me in welcoming my new/old colleague Dave Stokes, who just joined the MySQL Community Relations Team at Oracle as the new MySQL community manager for North America. Some of you may remember him from a previous stint at MySQL, where he was in charge of the MySQL certification program. Back then, he was already running the North Texas MySQL Users Group and a regular blogger on Planet MySQL. I am sure we will be seeing much more of these kind of activities from now on. So welcome aboard, Dave! I look forward to working with you.

As of today I am the MySQL Community Manager for North America. Part of the job description is work as part of a team that acts as the central resource and driving force for the design, process, manufacturing, test, quality and marketing of products(s) as they move from conception to distribution. So, you now have a focal point (me) to get your ideas into MySQL.

So help me gather and analyze information to define product specifications to move MySQL forward.

In my continuing MySQL 5.5 blog series, today I am covering what's new on the replication front.  MySQL replication is my favorite server feature and what drew me to MySQL during my tenure with Embarcadero Technologies.  Others seem to agree as based on community and customer surveys, MySQL replication is the most popular and widely used database feature.  Mostly because it is easy to set up and ease, it enables scalability and provides a pretty robust solution for data redundancy, backup and overall availability.  In MySQL 5.5 replication has been enhanced in response to user requests that MySQL replication:

• Ensure data consistency between master and slave servers
• Immediately detect if replication is not working
• Allow a crashed slave to automatically recover from the master relay log
• Allow users to filter …

I am happy to announce that MariaDB 5.2.3 is now released as a stable release.

During the gamma period we did not receive any serious reports for issues in 5.2, so we are relatively confident that the new code is of decent quality.

You can read about the features of MariaDB 5.2 in my previous blog entry or in the fast growing MariaDB knowledgebase..

What is most interesting about MariaDB 5.2 is that most of the features came from the MariaDB/MySQL community, not from Monty Program Ab!

Without the community it would not have been possible to do a stable release so soon after the last release. …