Re: Delete Query Taking Too Much Resources
SHOW CREATE TABLE DETAILS
--------------------------------
CREATE TABLE `notification` ( `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT, `memberlogin` varchar(255) NOT NULL DEFAULT '', `profile` varchar(255) NOT NULL DEFAULT '', `mess` varchar(255) NOT NULL DEFAULT '', `category` varchar(255) NOT NULL DEFAULT '', `type` varchar(255) NOT NULL DEFAULT '', `type_id` varchar(255) NOT NULL DEFAULT '', `viewed` enum('N','Y') NOT NULL DEFAULT 'N', `messagedate` bigint(20) NOT NULL DEFAULT '0', `recorddate` bigint(20) NOT NULL DEFAULT '0', `actioned` varchar(255) NOT NULL DEFAULT '', `temp` varchar(255) NOT NULL DEFAULT '', PRIMARY KEY (`id`), UNIQUE KEY `temp` (`temp`), KEY `memberlogin_category` (`memberlogin`(50),`category`(50)), KEY `recorddate` (`recorddate`) ) ENGINE=InnoDB AUTO_INCREMENT=1389 DEFAULT CHARSET=latin1
SHOW TABLE STATUS LIKE 'notification'
Name Engine Version Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Collation Checksum Create_options Comment
notification InnoDB 10 Compact 555 265 147456 0 114688 1620049920 1389 2011-08-29 15:38:31 latin1_swedish_ci
SHOW KEYS FROM notification
Table Non_unique Key_name Seq_in_index Column_name Collation Cardinality Sub_part Packed Null Index_type Comment Index_comment
notification 0 PRIMARY 1 id A 531 BTREE
notification 0 temp 1 temp A 531 BTREE
notification 1 memberlogin_category 1 memberlogin A 265 50 BTREE
notification 1 memberlogin_category 2 category A 531 50 BTREE
notification 1 recorddate 1 recorddate A 531 BTREE
I hope this will help you
THanks
Jaiswar Vipin Kumar R