Questions[indexing](server)

So, I have MySQL installed on my machine, and I need to change the ft_max_word_len, the maximum word length that MySQL will index. However, when I set it up via the tools provided, and query it, it still lists it as a max of 84 (I need 128+). When I try and use the command line, I get the following:

C:\>mysqld --ft_max_word_len=128
111210 23:55:46 [Warning] option 'ft_max_word_len': unsigned value 256 adjusted to 84
111210 23:55:46 [Warning] option 'ft_max_word_len': unsigned value 128 adjusted to 84

It should be noted, I tried to change it to 256 in the GUI tools, so that may be where that value is coming from. But why would I get both, and why can I not adjust this value?

Of note, I am on Windows 7, and MySQL 5.1.41 for 64bit.

Update: From @thinice's comment, this leads me to believe that this is a bug in MySQL (and from the sounds of it an mostly undocumented one, which I will need to change). So maybe my question is, would anyone have any inkling of how to change that value?

If you disable the keys (suspending indexing) on a mysql INNODB table, how long does that setting last?

For a query like:

ALTER TABLE users DISABLE KEYS;

Do the keys get re-enabled at the end of the script? or do they last until you explicitly turn indexing back on?

I have a table with 1.4 billion records. The table structure is as follows:

CREATE TABLE text_page (
    text VARCHAR(255),
    page_id INT UNSIGNED
) ENGINE=MYISAM DEFAULT CHARSET=ascii

The requirement is to create an index over the column text.

The table size is about 34G.

I have tried to create the index by the following statement:

ALTER TABLE text_page ADD KEY ix_text (text)

After 10 hours' waiting I finally give up this approach.

Is there any workable solution on this problem?

UPDATE: the table is unlikely to be updated or inserted or deleted. The reason why to create index on the column text is because this kind of sql query would be frequently executed:

SELECT page_id FROM text_page WHERE text = ?

UPDATE: I have solved the problem by partitioning the table.

The table is partitioned into 40 pieces on column text. Then creating index on the table takes about 1 hours to complete.

It seems that MySQL index creation becomes very slow when the table size becomes very big. And partitioning reduces the table into smaller trunks.

I have a large table which has a clustered index with an identity primary key. I'm deciding on the correct value for the fill factor for this table to minimise page splits. We maintain indexes using a script run daily which measures fragmentation and takes appropriate action. The table contains variable length columns.

My first thought was to set it at 100 (as records should only be written to then end of the table) but I assume that changes to the variable length columns could also cause page splits, so I'm now veering towards 90.

Any advice appreciated.

So I have a Windows XP SP 3 machine which is running Outlook 2007. When I search in Outlook for an email that exists using a basic keyword, like say "MySQL", I get no results. However, Outlook gives me the following message:

Search results may be incomplete because items are still being indexed. Click here for more details.

When I click, I get the following:

Outlook is currently indexing your items.
Search results may be incomplete because items are still being indexed.
8783 items remaining in "Mailbox - USER"
8812 items remaining across all open mailboxes.

The thing is, these are the numbers it has been reporting for several days, and Outlook is open for 8 hours a day. It does not seem like the index is working. As best I can tell, the index seemed to stop about 3 weeks ago.

How can I force Outlook 2007 to re-index everything and start working properly again?