Which tables I should convert to InnoDB?

[eh69]

Im using MyIsam now. I will convert my vbulletin tables to innodb, buty which? All? Some tables are small ex: vb_settings. Maybe myisam will be better for this table?

[Wayne Luke]

If you're going to switch, then you should switch all tables except the search* tables, session, and cpsession.

See:

http://www.vbulletin.com/forum/entry.php/2376-Part-1-vB4mance-Helping-communities-grow-performance-data-model-changes-in-vB-4-0

http://www.vbulletin.com/forum/entry.php/2413-Part-2-vB4mance-vBulletin4-Optimization-Basic-Guide-to-InnoDB-Conversion

http://www.vbulletin.com/forum/entry.php/2428-vB4Mance-Part-3-Database-performance-vB-benchmark-with-Percona-XtraDB-5-5-5-1

http://www.vbulletin.com/forum/entry.php/2430-vB4Mance-Part-4-The-Basics-Understanding-vBulletin4-PHP-Script-and-Hosting

http://www.vbulletin.com/forum/entry.php/2440-vB4Mance-Part-5-Expert-Level-Boosting-vBulletin-Performance-with-Advanced-Caching

[eh69]

Without search*?

http://www.vbulletin.com/forum/blogs/ibxanders/3935819-

alter table searchcore engine=InnoDB;

alter table searchgroup engine=InnoDB;

alter table searchlog engine=InnoDB;

So do convert or not?

[Zachery]

None of the search tables.

[eh69]

I have problem with some tables:
mysql> alter table vb_blog_text engine=InnoDB;
ERROR 1214 (HY000): The used table type doesn't support FULLTEXT indexes
mysql> alter table vb_language engine=InnoDB;
ERROR 1118 (42000): Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.

[Wayne Luke]

You won't be able to convert those tables.

[eh69]

im droped indexes title from vb_blog_text and converted this table.

[Zachery]

You won't be able to search the blog, or language tables then.

[eh69]

Are You sure? Searching now is working fine. I have vbulletin 4.2.2, not vb3...

[Wayne Luke]

Modifying the database like dropping indexes isn't supported. You're free to make whatever modifications to the code that you wish however we won't necessarily provide support for it.

If it works to your satisfaction then you're free to do what you want.

[eh69]

Okay. I will restore MyISAM tables od blog_text, vb_thread, vb_post, vb_language. postindex will be innodb too? this table is very large. have 15 000 000 records :P