EmergencyEMERGENCY? Get 24/7 Help Now!

More then 1000 columns – get transactional with TokuDB

 | September 25, 2014 |  Posted In: InnoDB, Insight for DBAs, Insight for Developers, MySQL, TokuDB

Recently I encountered a specific situation in which a customer was forced to stay with the MyISAM engine due to a legacy application using tables with over 1000 columns. Unfortunately InnoDB has a limit at this point. I did not expect to hear this argument for MyISAM. It is usually about full text search or […]

Read More

OpenStack users shed light on Percona XtraDB Cluster deadlock issues

 | September 11, 2014 |  Posted In: InnoDB, Insight for DBAs, MySQL, OpenStack, Percona MySQL Consulting, Percona XtraDB Cluster

I was fortunate to attend an Ops discussion about databases at the OpenStack Summit Atlanta this past May as one of the panelists. The discussion was about deadlock issues OpenStack operators see with Percona XtraDB Cluster (of course this is applicable to any Galera-based solution). I asked to describe what they are seeing, and as […]

Read More

When (and how) to move an InnoDB table outside the shared tablespace

 | August 22, 2014 |  Posted In: InnoDB, Insight for DBAs, MySQL, Percona MySQL Support, Percona Server for MySQL, TokuDB

In my last post, “A closer look at the MySQL ibdata1 disk space issue and big tables,” I looked at the growing ibdata1 problem under the perspective of having big tables residing inside the so-called shared tablespace. In the particular case that motivated that post, we had a customer running out of disk space in his […]

Read More

A closer look at the MySQL ibdata1 disk space issue and big tables

 | August 21, 2014 |  Posted In: Benchmarks, InnoDB, Insight for DBAs, MySQL, Percona MySQL Support

A recurring and very common customer issue seen here at the Percona Support team involves how to make the ibdata1 file “shrink” within MySQL. I can only imagine there’s a degree of regret by some of the InnoDB architects on their design decisions regarding disk-space management by the shared tablespace* because this has been a big […]

Read More