Ovais Tariq

Some people don’t probably know, but there is a difference between how indexes work in MyISAM and how they work in InnoDB, particularly when talking from the point of view of performance enhancement. Now since, InnoDB is starting to

MySQL

I had earlier written a post on tuning the MySQL server configuration [https://www.ovaistariq.net/358/tuning-mysql-server-settings/] which was more geared towards the MyISAM storage engine. While that is not because I didn’t intend on ignoring InnoDB but

MySQL

MySQL 5.5 has created a lot of hype and its not just hype, there are major performance enhancements not only in the MySQL server itself but in the newer InnoDB plugin shipped with MySQL 5.5. That’s exactly

MySQL

The more I go through others SQL, there are some common mistakes that I see developers making over and over again, so I thought why not start a series of tips that can help developers optimize their queries and avoid

MySQL

Just in case you don’t know resizing Innodb log file is not just simple as changing the value of innodb_log_file_size in the MySQL configuration file. But its even more simpler. Follow the following steps and you

MySQL

MyISAM has been the default storage engine for MySQL for years now. But that is soon going to change. With MySQL 5.5, Innodb is going to be the default storage engine (and I am pretty pleased about that, no

MySQL