be active again I need to
>>> restart the database, however aftewards I assume the tables will still
>>> be MyIsam.
>>>
>>> In this event I will need to manually alter each table, and I am
>>> concerned about the impact of this on the sy
I will need to manually alter each table, and I am
>> concerned about the impact of this on the system performance.
>>
>> Regards
>> Machiel
>>
>>
>> -Original Message-
>> From: John Daisley
>> To: Machiel Richards
>> Cc: mysql mailing list
mance.
Regards
Machiel
-Original Message-
From: John Daisley
To: Machiel Richards
Cc: mysql mailing list
Subject: Re: Changing database tables to different storage engine.
Date: Mon, 22 Nov 2010 10:51:23 +
I have frequently seen Innodb 'silently' disabled if the
innodb_l
On Mon, Nov 22, 2010 at 11:55 AM, Machiel Richards <
machiel.richa...@gmail.com> wrote:
>In this event I will need to manually alter each table, and I am
> concerned about the impact of this on the system performance.
>
That will indeed make for quite some locking time, depending on the
database tables to different storage engine.
Date: Mon, 22 Nov 2010 10:51:23 +
I have frequently seen Innodb 'silently' disabled if the
innodb_log_file_size is different to the files size on disk (quite
common when moving systems about). You wont be able to use innodb until
you re
I have frequently seen Innodb 'silently' disabled if the
innodb_log_file_size is different to the files size on disk (quite common
when moving systems about). You wont be able to use innodb until you resolve
this either by deleting the log files and restarting mysqld so they get
recreated or changi
Hi All
Sorry but things have now changed, and I found the following.
The tables was in fact restored as Innodb, however someone seems
to have gone and changed something causing innodb to be disabled, this
caused the tables to be defaulted back to MyIsam.
Should this not rath
