MySQL

On one of my Typo3 installations I found an unusually large InnoDB file (Typo3's indexed_search being the culprit).

dev.mysql.com/doc/refman/5.1/en/adding-and-removing.html is a bit more complex. Instead of mysqldump (step 1 per documentation) I ran this SQL statement, following Nickolay Pelov's suggestion.

Here are the SQL statements I used to create the scripts to shrink this file:

use information_schema;

Here are my notes from migrating an OSCommerce installation to a Drupal ubercart system.

Firstly dump all the products with their names and ids from the OScommerce database. Then import this data with the node import module. I've imported the id field into the description because at this point in time I couldn't figure where the sku was stored.

The Typo3 extension tt_news is causing problems with indexed_search. The table index_rel grows quickly to an enormous size, 28 million rows on one of my sites. This caused two problems:

• the nightly backups took a lot of time, the automated restore on the standby machine wouldn't even finish anymore.
• Typo3 search generated huge SQL queries that would bring down the MySQL server.

There is a lot of content on this site, but nowhere near 28 million "items" (whatever is in index_rel I do not know).