Moving DB from 3.23.58 to 4.0.25

[kevinmanphp2]

I am trying to move a large vBulletin mysql database from my old server using mysql 3.23.58 to a new dedicated server running 4.0.25. Unfortunately, I am getting errors on the import and vBulletin support is telling me that it is because of mysql version compatibility issues. Since my old server is shared hosting, I cannot upgrade the version. What can I do to make this DB migration work? How can I work around this? I look forward to your help. Thank you.

[Marco van Herwaarden]

Can you link me to the thread on vb.com regarding this issue?

[kevinmanphp2]

<a href="http://www.vbulletin.com/forum/showthread.php?t=153112" target="_blank">http://www.vbulletin.com/forum/showthread.php?t=153112</a>

[Marco van Herwaarden]

You never stated the mysql versions in that vb.com thread, you should have.

Do you have SSH/Telnet access to the old server also?
Did you check if the dump was complete (last few lines, should contain info about the Word table)
What options did you choose when creating the Export in phpMyAmin?

[kevinmanphp2]

You never stated the mysql versions in that vb.com thread, you should have.

Do you have SSH/Telnet access to the old server also?
Did you check if the dump was complete (last few lines, should contain info about the Word table)
What options did you choose when creating the Export in phpMyAmin?

Hey Marco... actaully I have been talking to Steve about this problem privately in member support. We moved the discussion there after my initial post linked above. Unfortunately I do not have SSH/Telnet access to the old server since it is on shared hosting at apollohosting.com. The dump did complete and when exporting I tried a .sql file using every combination of options avaiable :( . The options that I used on my first try was ADD DROP TABLE and AUTO INCREMENT only (of the 4 "Structure" options). I also attempted deleting all the DEFAULT CHARSET=latin1 engine lines from the dump file.