It’s been three long years since the last MySQLTuner release but you’ll now find version 1.
It’s no secret that Google Reader is a popular way to keep up with your RSS feeds, but it’s getting shelved later this year.
My quest to get better at Python led me to create a new project on GitHub.
If you push play, the video should scoot out to about the 14m40s mark where MySQLTuner appears on one of the slides.
The pv command is one that I really enjoy using but it’s also one that I often forget about.
·561 words·3 mins
Regardless of the type of hosting you’re using - dedicated or cloud - it’s important to take network interface security seriously.
If you’re running an operation on a large number of rows within a table that uses the InnoDB storage engine, you might see this error:
This problem has cropped up for me a few times, but I’ve always forgotten to make a post about it.
Users of PHPMyAdmin 3.
It has finally arrived.
If you have Excel files that need to be imported into MySQL, you can import them easily with PHP.
Thanks to some work started by Ville Skyttä, MySQLTuner is now included in Fedora 9 repositories:
·651 words·4 mins
If you run a fairly busy and/or badly configured MySQL server, you may receive something like this when attempting to connect:
Thanks to some hard work from Oden Eriksson and Frederik Himpe, MySQLTuner 0.
I found myself in a peculiar situation last week.
I’ve received some great feedback on my first screencast.
MySQL has quite a few cryptic error messages, and this one is one of the best:
I received an e-mail from Tim Linden about a post he made in his blog about backing up MySQL data to Amazon’s S3.
It’s tough to find examples of dumps that can’t be properly reimported on other servers.
To get the latest copy, head over to the download page!
Thanks to an e-mail from Joe Calderon, I’ve corrected a MySQLTuner bug where indexes were not being calculated properly when symbolic links are used.
One of the questions I receive the most is: “What version of Plesk works with MySQL 5?
A new version of MySQLTuner was released tonight to correct some bugs found within revision 26.
After a couple of weeks, my MySQL replication series has come to a close.
As some subversion users may have noticed, revision 23 of MySQLTuner was released quietly on Sunday.
There’s a few final configuration options that may help the performance of your slave MySQL servers.
If you want to make a DBA nervous, just let them know that they need to upgrade MySQL servers that are replicating in a production environment.
While many people might find replicating over an external network to be an odd concept, it does have some uses.
On some occasions, MySQL replication can break down if an statement comes from the master that makes no sense to the slave.
In a perfect world, slaves will contain the same data as the master at all times.
If you have a master with multiple slaves, you can get some performance and save money on hardware by splitting data horizontally among your servers.
An often overlooked benefit of MySQL replication is the ability to make reliable backups without affecting the integrity of the MySQL data.
Although performance is a much larger benefit of replication, it provides some redundancy for your application as well.
MySQL replication can increase performance by allowing developers to spread queries over two servers.
One of the topics I receive the most questions about is MySQL replication.
MySQL replication may sound complicated, but it can be done easily.
MySQLTuner revision 22 is available today.
After I was asked to create a stored procedure on a MySQL 5.
I’ve revamped a few of the recommendations in MySQLTuner, and revision 19 is now available tonight!
When you dump table data from MySQL, you may end up pulling a large chunk of data and it may exceed the MySQL client’s max_allowed_packet variable.