Helium Music Manager User Forum

[duens]

Hello!

I'm using Helium Music Manager with a MSSQL Database. Now I would like to convert this
database to MYSQL format. I did search the internet for a good open source software, and
found this one:
http://www.kofler.cc/mysql/mssql2mysql.html
I haven't tried it yet, because I'm not sure if the application above will convert my
Helium Music Manager MSSQL database correctly, with all the stuff and if nothing gets
lost. I'm not that into databases so I'm looking forward that somebody could tell me if
my DB will be converted correctly (with all the information etc.) if I'm using the application above?
Thanks for your advices.

// duens

PS If you know a better solution to convert a mssql database to mysql I would appreciate
to read about the solution, too. Thanks.

[Listener]

Just use the internel importing tool.
Open up Helium and connect to your MySQL database, then open Tools | Library | Management and click on the import button on the bottom. You will see the option to import a Helium Music Manager SQL Database, click on it and fill in the data, in the upcoming dialog, to connect to your old SQL database.

[duens]

Perfect! I'm too stupid to get the idea to check in Helium first. Thanks Listi.

[Shumaker212]

Not Sure that it will work for you but i use dbload to migrate my database and its says its a simple yet powerful tool to migrate database so look at it and try....

Find Here : http://www.dbload.com

[Listener]

That won't work - you can not simply convert these DBs because MySQL and MSSQL Helium databases (so databases that are created with Helium on these servertypes) are a bit different in their structure - so it is not possible to simply convert them or somethign the like. Please use the import database tool within the database manager in Helium

[Stefan Brueck]

Didn't want to start a new topic, because the subject nearly fits, I'm only interested about converting in both directions and about which one's the important one, eg. the one being the better choice to be used with Helium.

Having seen these lines, I thought this morning ... well if others are switching, why not having a try myself.
Everything works .. well I'd say "is on hold" if the better term, since MySQL seems to perform slower by factors not %tage.

Is that normal, or did I do something totally wrong ? I've also digged out some lines in here with recommendations about connections and timeouts, what sould work best with Helium.

A quick look at the running tasks till tell me that the Mysql task occupied up to 25% CPU speed for only switching between album browser and music explorer, which takes more but a handfull of seconds until the helium window finalised it's redraw.
Yes the sql task not the helium task, which shows me that it's not helium itself running into a speed problem.
Granted MySQL eats about a quarter of the memory MS SQL 2008 Express x64 did eat.

Thus a recommendation which SQL solution to be used best on Win 7 x64 would be nice.
Did search this forum for a while but without luck.

AMD quad, 4Gig Mem and db sitting on a VelociRaptor, so please don't tell me I need a solidstatedrive for the database.
And unfortunately I can't spent money für some dozens of VelociRaptors to store the tracks on them aswell. These must remain on a rpm 7200 drive.

help and recommendations appreciated