| Author |
 Topic  |
|
|
ian9001
Starting Member
22 Posts |
 Posted - 05 April 2006 : 19:01:54
|
About to move servers and migrate from MySql over to MS Sql.
Got a fair idea of how I intend to approach it, i.e. export to SQL format and import to MS Sql.
However, never done this before, and to be frank am a complete novice when it comes to MS Sql. So, anything I should look out for or pay attention to other than the obvious?
Any hints or pointers as to issues I may come up against will be gratefully received, on the basis that I'd rather pick yer brains before than come on here screaming for help when it all goes tits up because of a basic error on my part.
Thanks guys
Ian |
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 05 April 2006 : 20:46:20
|
I would first setup a test computer with mysql and sql server on it and then do some dry runs at converting the data.
I doubt you'll be able to use sql that's dumped by phpmyadmin or mysql administrator in ms sql. There are quite a few differences between the databases, different syntax, different datatypes, etc.
If Snitz is the only db app you're moving, use snitz to create a new sql server snitz db and then just import the data. You will need to take care that the record ID's get moved properly.
Access as an intermediate stop might be helpful.
|
======
Doug G
======
Computer history and help at www.dougscode.com |
 |
|
|
ian9001
Starting Member
22 Posts |
Posted - 06 April 2006 : 11:05:21
|
Thanks Doug, I'm in the process of setting up a dry run just now.
When you say Access as an intermediate stop, do you mean going down the route of MySQL ==> MS Access ==> MS Sql?
Ian |
|
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 06 April 2006 : 15:28:30
|
quote:
Originally posted by ian9001
Thanks Doug, I'm in the process of setting up a dry run just now.
When you say Access as an intermediate stop, do you mean going down the route of MySQL ==> MS Access ==> MS Sql?
Ian
It depends on how easy or difficult it is to get your data moved. You may be able to simply set up a DTS job to move data directly from mysql to mssql. If you experience problems, though, access has easy built-in tools to inspect/manipulate the data and connects pretty easily to sql server.
BTW, I've never done a migration from mysql to mssql :)
|
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
|
ian9001
Starting Member
22 Posts |
Posted - 21 April 2006 : 08:02:37
|
Just a quick follow up to this server move as it may be of use to someone else in the future.
I was unable to set up a DTS job so had to manually move the data over and I took Doug's advice and used MS Access as a migration tool.
I created a forum with an empty MS Access database (other than admin), ran the Mod setup files to create the extra tables and fields. Exported the complete forum from the MySql server in XML format and then imported it into the MS Access database.
I had tried other formats, e.g. SQL, CSV etc, but in practise found that XML was error free whereas the others caused problems with the topic and reply tables.
I then created a forum with an empty MsSql database, ran the Mod setup files as before to create the tables and fields on the new server. I then used MsSql's import facility to import the complete MS Access database.
Other than a few issues with the Photo Album Mod and some admin configurations, it all worked a treat and the forum is working as before. Testing import/export formats aside, total time to do change over about 30mins.
Ian
|
|
|
| |
Topic |
|
Topic Locked
