MySQL 5.6 parameters

I have been performing a few MySQL upgrades from 5.5 to 5.6.   It is general a straight forward process but I wanted to discuss MySQL 5.6 parameters changes.

Oracle....the small things

I have been neglecting my blog recently and decided to devote a page to some of the small things I have done.   They are not necessarily about how something works instead some are showing syntax and others useful things.  Also this is a reminder for myself something.  I will be adding to this page with more stuff.
Oracle - CREATE TABLE <name> AS........
The Oracle Recycle Bin
Oracle - Getting the DDL for an object
Corrupt UNDO segment. 
Loading Large Tables with a PK

Oracle silent and response file install

Recently whilst installing an Oracle client on a server I found the server had no X client on it.  This posed the problem of how to install without the Oracle OUI.  I remember back whilst trying to perform a silent install on a 10G database and having countless issues with my response file (rsp). 

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!).