MySQL Finding Index Information

Going to make this short and sweet.  I was recently dealing with an index and want to know the size of one specific index on a table.

Url for new improvements in MySQL 5.6

A good reference url for new improvements in MySQL 5.6

http://www.mysqlperformanceblog.com/2013/01/27/mysql-5-6-improvements-in-the-nutshell/

Partitioning MySQL 5.6 Style

One of the major feature enhancement in MySQL 5.6 is partitioning.    We use partitioning on a table that stores archive data.  The data is partitioned via a date range.  Pre 5.6 we had to select the specified range for reporting.  Now with some code modification we can select the exact partition.

MySQL Tuning Parameter

I haven't posted anything in a while.  The holiday season has been busy and I have been complete upgrade projects.  Before I start belated Happy New Year to you.

Whilst working on a small client database recently and made a list the MySQL parameters we used to tune the database.  Hopefully it may give you some pointers into database tuning and parameters to look at.  I should give you a couple of more details the database is fairly large about 3TB.  It's a mix of online and archive data.  It's main transaction types are insert and select.  The database version is 5.5.11 (soon to be upgraded to 5.6.14).  The databases within the instance are mainly innodb.


MySQL Upgrade and Compressed Tables

Recently one of our MySQL servers crashed.  Luckily there wasn't any damage but after a support call it was found it was due to a bug with the version we are running.  We decided to upgrade to the latest version of 5.5.  We have one physical server running 10 small to medium MySQL instances (no replications).  Whereas 9 of the upgrades went as planned one didn't (there is always one!).

MySQL Locking (Version 5.5)

Locking in MySQL seems more complicated to follow than in other database.  Monitoring in MySQL is better with the MySQL Enterprise Monitor but for all the command line people, it is more difficult to find out what is locking/blocking.

Upgrading MySQL to 5.5.32 and compressed tables

Recently I was tasked with upgrade some MySQL instances from 5.5.16 to 5.5.32.  The task seemed easy enough but when I started the process on one of the larger databases on the server (just under 1TB), it is made up of a lot smaller tables and most over 90% are 'myisam'.  I ran into issues when I ran mysql_upgrade.

error : Table upgrade required. Please do "REPAIR TABLE `<name>`" or dump/reload to fix it!