| Author |
 Topic Search  Topic Options
|
highinfidelity 
Newbie
Joined: 22 April 2005
Location: Italy
Status: Offline
Points: 20
|
 Post Options
 Thanks(0)
 Quote  Reply
 Posted: 19 May 2009 at 10:02am |
MortiOli, please let me thank you for the help you're giving, I knew that the conversion was going to be all but troubleless. That's why I hoped someone who already did it and was more experienced in the database structure was going to do it.
I have fixed yesterday's error. There actually was some crap amid the dates, probably a leftover of a hacking we had two years ago.
However, now I get this:
Moving all the users...
Microsoft JET Database Engine error '80040e21'
The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again.
/admin/database/convert.asp, line 86
Please note that I compacted the database before uploading, so I'd say that's not the issue. Any idea?
|
 |
MortiOli
Senior Member
Joined: 26 May 2002
Location: United Kingdom
Status: Offline
Points: 514
|
Post Options
Thanks(0)
Quote Reply
Posted: 19 May 2009 at 10:22am |
No problems - I'll assist as much as I can, but I've forgotten everything I did / ran into when we made the conversion script.
Could you check your database, and see what the last user was that was moved over? I'm guessing it may have run into problems with the Guest user that WWF uses.
|
|
highinfidelity
Newbie
Joined: 22 April 2005
Location: Italy
Status: Offline
Points: 20
|
Post Options
Thanks(0)
Quote Reply
Posted: 20 May 2009 at 9:47am |
Hi there and thanks for your hint. The problem was different but you have given me the strategy to track it down (and track down other few errors, much less than I feared at the beginning). Now the coversion program runs freely. After having replaced the three extra files to gain access with old passwords, I could log in and see that the conversion has been done pretty well.
Okay. Now the next step is to migrate from Access to mySQL. Any idea from where to start, since version 7 is no longer supported? I remeber there WAS a way to do it, or I would have never started digging in this complicated migration thing...
|
|
MortiOli
Senior Member
Joined: 26 May 2002
Location: United Kingdom
Status: Offline
Points: 514
|
Post Options
Thanks(0)
Quote Reply
Posted: 20 May 2009 at 12:35pm |
Glad to hear it's run ok! Might be best to post the problems you've ran into, and how you fixed them, in case anyone else has an issue with the conversion.
Is there any files in the v7 forum you've got, which does the Access to MySQL conversion? I've got a feeling that the forum comes bundled with upgrade tools to do it.
EDIT - You might be best upgrading from v7 to v9 first, then upgrading from Access to MySQL!
|
|
highinfidelity
Newbie
Joined: 22 April 2005
Location: Italy
Status: Offline
Points: 20
|
Post Options
Thanks(0)
Quote Reply
Posted: 20 May 2009 at 1:44pm |
Nothing special, really: the author_name table had some duplicated entries of users who had been deleted. It's weird as those things are handled automatically by Snitz, and the conversion program tracks them down. However, for some reason, in the end I still had duplicate usernames in the table and had to delete them at hand.
After having done this, the conversion program stops again at every post made by one of those duplicate users (because the record is fatherless). I changed the user_ID number into another existing user_ID number (okay that'e not fair, but who cares? perhaps I will delete those posts later) until the program performed its whole task.
I will check if there is some access->mySQL facility included in the software, I don't remember one being there. Is there some specific reason why you think it is better to upgrade to v9 first, and later to mySQL? Our forum is graphically highly customized and all files had been prepared four years ago, when we first thought to move here. Unfortunately I see that bakcward compatibility has not been taken in account (all icons' dimension has been changed in v9, as far as I see, so I would need to redraw all icons one by one) so I don't know if we actually want to move from v7 at all while a V10 is on its way, and then V11, and then V12... Each time with all things to be redone from scratch.
By the way I remember there was a webwiz name removal option that was quite cheap, while now I only see a software purchase option at a very high price. Is the name removal option gone? Other bad news indeed.
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 20 May 2009 at 3:09pm |
|
I would use the database upgrade tools to upgrade from version 7 to version 9 first, before moving databsse types.
mySQL is a very different database to the Microsoft ones as it is not a relational database so the schema is very different, also see issues with corrupted database with mySQL that you never see with SQL Server.
Instead I would suggest upsizing from Access to SQL Server. Web Wiz Forums runs great on teh free Express Edition of SQL Server and will run more stabily.
There are no dimensions hardcoded into web wiz forums to make it simple to replace images with those of different sizes.
Allot of work was done between version 7 to version 8 with a new forum engine which is much more secure and stable than with version 7, which dates back to an engine built about 7 years ago now.
|
|
|
|
highinfidelity
Newbie
Joined: 22 April 2005
Location: Italy
Status: Offline
Points: 20
|
Post Options
Thanks(0)
Quote Reply
Posted: 22 May 2009 at 7:56am |
Thanks for your input, I of course followed your hints. I'm now to V9, the upgrading tools worked as a breeze, although now I have problems with accented letters in the topics and the joining dates of members are all separated by question marks "?". But will try to fix it later.
Now the important step is to migrate from Access to mySQL. Is there some "official" tool to do it? I couldn't find any, event though I've read that many people did it before with success. Any help will be greatly appreciated...
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 22 May 2009 at 8:35am |
|
I would NOT recommend going from Access to mySQL. Some people have managed it, but we tend to find that they have allot of stability issues as the mySQL version uses a completely different schema as it is not a relationional database like Access and SQL Server, has difefernt data types, and handles dates difefrently.
If you wanted to move from Access to mySQL then we would not support it and you should be awware that you WILL have problems.
You should instead upsize the database to SQL Server using the upsize wizard in Access to the conversion.
|
|
|
|
