Be careful rotating MySQL logs
If you enable logging of all queries as “slow queries” using the patch or MySQL 5.1 you can get log file to grow huge. Same may happen with general log file. In some cases we’ve got log file sizes of...
View ArticleUsing Flexviews – part two, change data capture
In my previous post I introduced materialized view concepts. This post begins with an introduction to change data capture technology and describes some of the ways in which it can be leveraged for your...
View ArticleClik here to view.
How to recover deleted rows from an InnoDB Tablespace
In my previous post I explained how it could be possible to recover, on some specific cases, a single table from a full backup in order to save time and make the recovery process more straightforward....
View ArticlePercona welcomes Drizzle 7.1
The Drizzle team has published the first Drizzle 7.1 stable release. The announcement on the Drizzle blog covers some of the major improvements in this release over the previous stable release, Drizzle...
View ArticleRecovery deleted ibdata1
Recently I had a case when a customer deleted the InnoDB main table space – ibdata1 – and redo logs – ib_logfile*.MySQL keeps InnoDB files open all the time. The following recovery technique is based...
View Article