June 19, 2013

Post: How innodb_open_files affects performance

… allocated in system tablespace. So if you create Innodb tables you better store some data in them otherwise …InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files… InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer… InnoDB

Comment: How would you compress your MySQL Backup

restoring from that dump file. In any case I`ve encountered I`ve had problems with restoring InnoDB tables larger then 2KK rows. The restore… interesting to have a case study on a medium database restore with different server settings. I was planning to have this… should they be changed in order to obtain a faster restore. What should there be optimized to obtain this? I m…

Post: How to recover deleted rows from an InnoDB Tablespace

… because we don’t have a backup or the backup restore process doesn’t work. How can I recover deleted rows… JOIN INNODB_SYS_TABLES as t USING(TABLE_ID) WHERE t.NAME=’salaries’; +———-+———+ | INDEX_ID | NAME | +———-+———+ | 26 | PRIMARY | | 27 | emp_no | +———-+———+ B) InnoDB Table Monitor… related with tables and indexes (with their IDs) to the error log. mysql (employees) > CREATE TABLE innodb_table_monitor (id int) ENGINE=InnoDB; TABLE: name employees…

Post: InnoDB: look after fragmentation

…`) ) ENGINE=InnoDB Table has 11864696 rows and takes Data_length: 698,351,616 bytes on disk The problem is that after restoring table from…: 11569733 # InnoDB_IO_r_ops: 38530 InnoDB_IO_r_bytes: 631275520 InnoDB_IO_r_wait: 0.204893 # InnoDB_rec_lock_wait: 0.000000 InnoDB_queue_wait: 0.000000 # InnoDB_pages…

Post: Should you move from MyISAM to Innodb ?

… but will start taking way too much time to do restore for Innodb. On large scale installations mysqldump does not work anyway… storage engine (typically Innodb) and when use other tables when it really gives substantial gains. I would not switch table to MyISAM because… it can be as much as 10-50 times for Innodb tables in particular for write intensive workloads. Check here for details…

Post: Using INFORMATION_SCHEMA instead of shell scripting

… engine=’innodb‘ into outfile ‘/tmp/dump.sh’; Query OK, 328 rows affected (46.88 sec) In other case I needed to restore Innodb tables from mysqldump because of corrupted Innodb tablespace – to do this I had to clean all .frm files which correspond to innodb tables

Post: Moving from MyISAM to Innodb or XtraDB. Basics

… feature differences between MyISAM and Innodb though well it is typically easily spotted by converting tables to Innodb on restored backup. Full text search… in MyISAM but would not fit to Innodb, though this is an exception. Space Innodb Tables tend to be larger. Again converting schema…

Post: Add an option to Fail on Innodb Initialize failure, Please ?

… MySQL does not stop if Innodb storage engine failed to initialize but starts properly… just having Innodb tables unavailable. I honestly do not… accessing Innodb tables is also very obfuscated: error : Incorrect information in file: ‘./prod/user.frm’ How this supposed to tell you Innodb (or… message and think it is indeed .frm corruption – trying to restore .frm from backup or other servers and being extremely frustrated…

Post: MySQL Backup tools used by Percona Remote DBA for MySQL

… to mysqldump Consistent backups between myisam and innodb tables. Global read lock only held until myisam tables are dumped. We are researching into… to make restoring single tables easy. You can quickly restore a single table, instead of restoring your entire backup just to find a tiny table you…

Comment: Should you move from MyISAM to Innodb ?

… for restores, selective restoring from binary files is painful in InnoDB. If you weren’t using LVM and doing raw backups w/ InnoDB, > you probably weren’t backing your databases up properly either. For per-table restores, we use mysqldump + â… that we would have to restore a table from tape to deal with some kind of unknown situation. InnoDB was not built for…