If it works fine currently, the rule usually is: don't mess with it. :) I
would stick with MyISAM if I were you, it should be plenty good enough for
such a small table and usage as you described.
If you are experiencing performance issues, I would recommend looking at
indexes if you haven't alread
PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 14, 2005 7:00 PM
To: Stembridge, Michael
Cc: mysql@lists.mysql.com
Subject: Re: Considering migration from MyISAM to InnoDB
see the my.cnf examples in the install dir, and look at innodb* variables.
you can migrate each table just using :
alte
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 14, 2005 7:00 PM
> To: Stembridge, Michael
> Cc: mysql@lists.mysql.com
> Subject: Re: Considering migration from MyISAM to InnoDB
>
> see the my.cnf examples in the install dir, and look at innodb* variables.
>
see the my.cnf examples in the install dir, and look at innodb* variables.
you can migrate each table just using :
alter table toto engine=innodb;
Mathias
Selon "Stembridge, Michael" <[EMAIL PROTECTED]>:
> I currently use MyISAM on an internal web application server; our data takes
> up 10mb a
I currently use MyISAM on an internal web application server; our data takes
up 10mb at this time, though this is likely to grow substantially in the
coming year. The database sees moderate heavy read and moderate write usage
from 50 users.
We're upgrading our sever from Red Hat 7.3 to SuSE
