May 18, 2013

How to recover table structure from InnoDB dictionary

April 22, 2013 By 4 Comments

To recover a dropped or corrupt table with Percona Data Recovery Tool for InnoDB you need two things: media with records(ibdata1, *.ibd, disk image, etc.) and a table structure. Indeed, there is no information about the table structure in an InnoDB page. Normally we either recover the structure from .frm files or take it from [...]

Filed Under: Insight for DBAs, MySQL Tagged With: , , , , , ,

Understanding the maximum number of columns in a MySQL table

April 8, 2013 By 5 Comments

This post was initially going to be two sets of polls: “What is the maximum number of columns in MySQL?” and “What is the minimum maximum number of columns in MySQL?”. Before you read on, ponder those questions and come up with your own answers… and see if you’re right or can prove me wrong! [...]

Filed Under: MySQL Tagged With: , , , , , , , ,

MySQL Backup tools used by Percona Remote DBA for MySQL

March 13, 2013 By 8 Comments

As part of Percona Remote DBA for MySQL service we recognize that reliable backups are one of the most important things we can bring to the table. In my experience handling emergencies, the single worst thing that can happen is finding out you don’t have backups available when some sort of data loss or catastrophic [...]

Filed Under: Cloud and NoSQL, Insight for DBAs, Insight for Developers, MySQL Tagged With: , , , , , , , ,

InnoDB Full-text Search in MySQL 5.6 (part 1)

February 26, 2013 By 1 Comment

I’ve never been a very big fan of MyISAM; I would argue that in most situations, any possible advantages to using MyISAM are far outweighed by the potential disadvantages and the strengths of InnoDB. However, up until MySQL 5.6, MyISAM was the only storage engine with support for full-text search (FTS). And I’ve encountered many [...]

Filed Under: Insight for DBAs, Insight for Developers, MySQL Tagged With: , , , , ,

Is there room for more MySQL IO Optimization?

January 3, 2013 By 11 Comments

I prefer to run MySQL with innodb_flush_method=O_DIRECT in most cases – it makes sure there is no overhead of double buffering and I can save the limited amount of file system cache I would normally have on database server for those things which need to be cached — system files, binary log, FRM files, MySQL [...]

Filed Under: Insight for DBAs, MySQL Tagged With: , ,

Why ALTER TABLE shows as two transactions in SHOW ENGINE INNODB STATUS

July 1, 2012 By 4 Comments

When executing an ALTER TABLE, InnoDB (and XtraDB) will create two InnoDB transactions: One transaction is created when the table being ALTERed is locked by the server. This will show up as something like “TABLE LOCK table `schema`.`table_name` trx id XXXX lock mode S” in SHOW ENGINE INNODB STATUS. Another is created when adding or [...]

Filed Under: Insight for DBAs, MySQL

Percona XtraDB Cluster Feature 1: High Availability

January 17, 2012 By 20 Comments

There and in coming posts I am going to cover main features of Percona XtraDB Cluster. The first feature is High Availability. But before jumping to HA, let’s review general architecture of the Percona XtraDB Cluster.

Filed Under: Insight for DBAs, MySQL, Percona Software

Percona XtraBackup 1.6.4

December 19, 2011 By 9 Comments

Percona is glad to announce the release of Percona XtraBackup 1.6.4 on 19 December, 2011 (Downloads are available here and from the Percona Software Repositories). These release notes are (as always) available from the online Percona XtraBackup documentation. This release is purely composed of bug fixes and is the current stable release of Percona XtraBackup. In this release we now [...]

Filed Under: MySQL

MySQL opening .frm even when table is in table definition cache

November 21, 2011 By 8 Comments

or… “the case of Stewart recognizing parameters to the read() system call in strace output”. Last week, a colleague asked a question: I have an instance of MySQL with 100 tables and the table_definition_cache set to 1000. My understanding of this is that MySQL won’t revert to opening the FRM files to read the table [...]

Filed Under: MySQL

Connecting orphaned .ibd files

May 13, 2011 By 19 Comments

There are two ways InnoDB can organize tablespaces. First is when all data, indexes and system buffers are stored in a single tablespace. This is typicaly one or several ibdata files. A well known innodb_file_per_table option brings the second one. Tables and system areas are split into different files. Usually system tablespace is located in [...]

Filed Under: MySQL
« Older Posts