June 20, 2013

Post: MySQL Query Patterns, Optimized - Webinar questions followup

the STRAIGHT_JOIN, the query optimizer reordered the tables.  It seemed to prefer an index-scan of 7 rows in the `kind_type` table to

Post: The small improvements of MySQL 5.6: Duplicate Index Detection

the table ‘test.test’. This is deprecated and will be disallowed in a future release. 1 row in set (0.00 sec) As theto get more familiar with this and other particularities of the latest MySQL GA release, have a look at our upcoming sessions for the “Moving to

Post: How to recover deleted rows from an InnoDB Tablespace

get the table row format from the Information Schema: mysql (information_schema) > SELECT ROW_FORMAT from TABLES WHERE TABLE_SCHEMA=’employees’ AND TABLE_NAME

Post: Using Flexviews - part two, change data capture

the local machine which is the usual configuration for Flexviews since it requires local access to the tables and the changelogs in order toand then insert some more of them: mysql> create table > test.demo ( > c1 int auto_increment primary key, > c2 int > ) > engine=innodb; Query

Post: InnoDB Full-text Search in MySQL 5.6 (part 1)

and it appears to work fine. But here’s where things start to get even weirder. According to the documentation, if we specify the name of a table

Post: Can MySQL temporary tables be made safe for statement-based replication?

table test.t(a int) engine=innodb *************************** 3. row *************************** Log_name: mysql-bin.000011 Pos: 211 Event_type: Querytyping COMMIT, the rest of the statements go into the binlog. It appears to me that there’s no way to get the CREATE TEMPORARY TABLE statement to

Post: MySQL 5.6 vs MySQL 5.5 and the Star Schema Benchmark

the full table scans access the table by primary key.  This forces the storage engine to touch the same page numerous times in rapid succession.  This invariably moves the

Post: ANALYZE: MyISAM vs Innodb

query execution. I typically look at ANALYZE TABLE and adding it to the table if I see having it run helps to get good plans. If queryTable | Non_unique | Key_name | Seq_in_index | Column_name | Collation | Cardinality | Sub_part | Packed | Null | Index_type

Post: Updated msl (microslow) patch, installation walk-through!

to log only queries doing full table scans you would need to set this to “full_scan”, while in order to getand the file may grow huge very quickly when logging all the queries. This parameter allows you to get the

Post: Researching your MySQL table sizes

queries to find space used by particular tabletype” in sharded environment when multiple tables with same structure and similar name exists: SELECT count(*) tables, concat(round(sum(table