We moved directly from 4.0.20 to 5.0.16. Worked like a charm. I had a
script that went through and optimized all tables with keys on
text/varchar and char fields.
We're also slowly ALTERing innodb tables to get them into the new
compact format.
On 12/28/05, Gleb Paharenko <gleb.paharenko@stripped> wrote:
> Hello.
>
>
>
> Manual recommends to perform an upgrade step by step. So
>
> I suggest you to move to 4.1 at first. When you said 'tablespace'
>
> have you meant that you're using InnoDB tables? I'm not sure about
>
> them, check the change logs to find out any incompatible changes. In
>
> case of MyISAM,very often it is enough just to copy files to the
>
> directory of the new server and repair indexes.
>
>
>
>
>
>
>
>
>
> Tripp Bishop wrote:
>
> > Howdy all,
>
> >
>
> > I've got a MySQL 4.0.24 database that I'd like to
>
> > upgrade to 5.0.15. Is it possible to backup the
>
> > tablespace "file" in the mysql data directory and then
>
> > install the new database then move the backed up files
>
> > into the new installations data directory? Are we
>
> > stuck running a mysqldump script? That would take
>
> > hours and we'd like to avoid it if at all possible. If
>
> > not we'll deal with it but it would be nice to just
>
> > move the files.
>
> >
>
> > Thanks,
>
> >
>
> > Tripp
>
> >
>
> >
>
> >
>
> >
>
> > __________________________________
>
> > Yahoo! for Good - Make a difference this year.
>
> > http://brand.yahoo.com/cybergivingweek2005/
>
> >
>
>
>
> --
> For technical support contracts, goto https://order.mysql.com/?ref=ensita
> This email is sponsored by Ensita.NET http://www.ensita.net/
> __ ___ ___ ____ __
> / |/ /_ __/ __/ __ \/ / Gleb Paharenko
> / /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenko@stripped
> /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
> <___/ www.mysql.com
>
>
>
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
>
>
