Jul 02, 2014 |
Cloud, Insight for DBAs, MySQL
I recently had an opportunity to migrate a customer from a physical server into Amazon’s RDS environment. In this particular case the customers’ platform makes extensive use of MySQL triggers and views. I came across two significant issues that prevented me from following Amazon’s documentation, which basically states “use mysqldump” but doesn’t call out a […]
Dec 13, 2013 |
Insight for DBAs, MySQL, Percona Services
Recently I was working with a customer where we noticed that Seconds_Behind_Master fluctuating from an expected value of 0 seconds behind to a fairly high six figure value. The servers were configured in a master-master relationship and used 5 figure server_id values, and we had just migrated this cluster from one data centre to another […]
Jun 04, 2013 |
Insight for DBAs, Insight for Developers, MySQL
Lately I have been working with a set of customers on a longer term basis which has given me time to explore new tools using their environments. One tool that I am finding very helpful is called SchemaSpy. SchemaSpy is a Java-based tool (requires Java 5 or higher) that analyzes the metadata of a schema in […]
Oct 19, 2012 |
Insight for DBAs, Insight for Developers, MySQL
Did you just run an UPDATE against your 10 million row users table without a WHERE clause? Did you know that in MySQL 5.5 that sometimes you can recover from a bad UPDATE statement? This is possible if you are running in binlog_format=ROW ! Imagine this scenario:
|
CREATE TABLE `t1` ( `c1` int(11) NOT NULL AUTO_INCREMENT, `c2` varchar(10) NOT NULL, PRIMARY KEY (`c1`) ) ENGINE=InnoDB; INSERT INTO `t1` (`c2`) VALUES ('michael'), ('peter'), ('aamina'); |
We run an accidental UPDATE statement that […]
May 30, 2012 |
Insight for DBAs, Insight for Developers, MySQL, Percona Software
Have you wanted to compress only certain types of columns in a table while leaving other columns uncompressed? While working on a customer case this week, I saw an interesting problem where a table had many heavily utilized TEXT fields with some read queries exceeding 500MB (!!) and stored in a 100GB table. In this […]