Results 1 to 5 of 5

Thread: Converting to InnoDB

  1. #1
    Proware's Avatar
    Proware is offline A Prolific Poster
    Join Date
    Mar 2006
    Location
    Sydney Australia
    Posts
    310

    Default Converting to InnoDB

    I have enabled InnoDB in MySQL but have a question.

    Do I also need to convert all / individual files to have an InnoDB table type instead of MyIsam?
    Cheers

    David Younger
    TSM - The Service Manager
    http://www.theservicemanager.com


    Operating system type and version: Windows 2003 Server
    » Sugar Suite version 4.5.1e Professional
    » Webserver type and version Microsoft-IIS/6.0
    » PHP version 5.2.6
    » MySQL server version 5.0.51a

  2. #2
    dstrickler is offline Sugar Community Member
    Join Date
    Mar 2006
    Posts
    77

    Default Re: Converting to InnoDB

    While not expert on this, I switched today from InnoDB from MyISAM, and had to dump and reload our tables. Note that after the dump, I edited the dump file and changed all text that said "MyISAM" to "InnoDB". Then I reloaded the data.

    That worked just fine, and even seemed to re-create the indexes, etc.

    Note, for 71MB of dumped data, it took a few hours to import on a rockin' new server.
    Dave Strickler
    MailWise LLC
    www.mailwise.com
    Intelligent Email Protection, compatible with Sugar




  3. #3
    dstrickler is offline Sugar Community Member
    Join Date
    Mar 2006
    Posts
    77

    Default Re: Converting to InnoDB

    I found a short, but well written article on the upgrade: http://software.newsforge.com/softwa...1.shtml?tid=72
    Last edited by dstrickler; 2006-10-01 at 03:26 AM.
    Dave Strickler
    MailWise LLC
    www.mailwise.com
    Intelligent Email Protection, compatible with Sugar




  4. #4
    hypo.jb is offline Junior Member
    Join Date
    Sep 2006
    Posts
    3

    Default Re: Converting to InnoDB

    Quote Originally Posted by dstrickler
    While not expert on this, I switched today from InnoDB from MyISAM, and had to dump and reload our tables. Note that after the dump, I edited the dump file and changed all text that said "MyISAM" to "InnoDB". Then I reloaded the data.

    That worked just fine, and even seemed to re-create the indexes, etc.

    Note, for 71MB of dumped data, it took a few hours to import on a rockin' new server.

    You could have taken a snapshot (mysqldump) of the DB in myISAM then created an empty DB using the InnoDB engine then ran the script...

    and 71MB = few hours??? on a new server? can you describe what you were doing that it took such a long time?

  5. #5
    dstrickler is offline Sugar Community Member
    Join Date
    Mar 2006
    Posts
    77

    Default Re: Converting to InnoDB

    Quote Originally Posted by hypo.jb
    You could have taken a snapshot (mysqldump) of the DB in myISAM then created an empty DB using the InnoDB engine then ran the script...

    and 71MB = few hours??? on a new server? can you describe what you were doing that it took such a long time?
    When I ran it the 2nd time (after some minor InnoDB tuning params), it took under 4 minutes. ;-)

    Server is a Compaq DL360. Dual 3.6ghz Xenon CPUs, 5GB of RAM, SCSI RAID 0 (just a mirror). Running MySQL5, Ubuntu, and PHP5. Oh and v4.5c of Sugar ;-)
    Dave Strickler
    MailWise LLC
    www.mailwise.com
    Intelligent Email Protection, compatible with Sugar




Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •