When transitioning MySQL database from Windows to Linux, users often encounter issues related to case-sensitiveness. Windows is case-insensitive and Linux is case-sensitive. In such scenarios when a database call is made after the application migration happens, users often run into errors which can send them in circles between the migration servers. Solution to this problem is to add a single line of text under my.cnf (MySQL configuration file) under [mysqld] (more…)

When new fileds are created as variable characters they get stored as latin1_swedish_ci as default. To change the default collation users will have to manually select the collation of their choice from the mysql admin interface such as in the case of phpmyadmin or will have to denote it in sql queries. To make a specific collation as the default, other option to give mysql an indication of it by having the needed collation name in my.cnf (mysql configuration) as shown below Edit my.cnf: [mysqld] collation_server=latin1_general_ci (more…)

Reason for the error is the availability of space allocated to the MySQL database in the specified partition. Easy fix for this is to go to the PhpMyAdmin interface (via CPanel/WHM) and identify the tables which has some value in under overhead column. Select ALL those tables and choose the option "Repair table" after you ensure that there is enough space in the database.

HeidiSQL - a comprehensive tool for MySQL management which is available for Free. Manage data tables, export/import databases, synchronise tables between databases, integrity check, database backup service management, edit database content and many more features packaged as a solution for ALL your MySQL needs. This runs on windows platforms - WinXP/XP7 and you can download HeidiSQL from Download link (more…)

Full backup Full backup is process of backing up ALL data. First step towards all other types of backup Backup time will be longer Restore operation takes less time Differential backup Differential backup is the process of backing up data that has changed since the last FULL backup. Requires file maintenance as the backup file will be of similar size or larger than its previous backup Longer backup time than incremental backup Faster restoration than incremental backup Incremental backup Incremental backup is the process of backing up data that has changed since the last Full, Incremental or Differential backup Takes lesser backup time as it will have small data to archive Takes longer restoration time Mirror backup Mirror backup is similar to full backup and is a direct copy of the files/folders Files are not compressed in zip files and are not protected with password. They remain the mirror or exact copy of the source.

When moving mysql database from one server to another or, to test that the data backup works as expected we need to import mysql dump file in the testing environment. Create the database (test-database) in the testing environment and identify the location of the .gz or .sql file. If the mysql dump was a .gz file, you need to gunzip to uncompress the file by typing $ gunzip mysqldump.sql.gz This will uncompress the .gz file and will just store mysqldump.sql in the same location. (more…)