views:

1054

answers:

4

For a new project I have to import the pre-existing data from MySql.

In this site I have found many options, some including the installation of drivers. What is the fastest & easiest way to do it?

Update: this would be just a one time import

A: 

You've linked to connectionstrings but I'm not sure why.

Will this be a one time import or will it be an ongoing thing?

GregD
Hi, I linked connectionstrings because it is a list of ways to connect to MySql and I don't know wich one is easier
Dawkins
+1  A: 

Convert Mysql to Mssql database

Take a look to free software which migrate databases.

Fred
I am going to use Toad wich seems to export to Excel and its free.
Dawkins
A: 

If you have access to phpMyAdmin you could run an export of the entire database. It will generate a long list of SQL commands to create all the schema and optionally insert all the data into their respective places.

It is also possible to perform all this from the command line.

If you have a lot of data you may want to do it all in pieces, single SQL scripts for each table and the inserts into each.

Then on the M$ SQL side just create the database, connect to it with SQL Query Analyzer or SQL Management Studio, copy-n-paste your SQL scripts into the window and execute.

Chances are a majority of your MySQL code will just work in M$SQL. If you run into issues, you can set a compatibility level on the MySQL export to fit your destination environment better.

If your just doing data, as long as the schema's match up, all you have to script is the data import/export, don't script the schema and CERTAINLY DON'T script drops!!!

EDIT: if you had to do any transformations, I believe you can export to M$ Excel, certainly to a CSV, then on the M$SQL import do your mappings and such.

Adam
Are you sure that all Mysql Data Types are compatible with Mssql Data Types???
Fred
A: 

My team recently did the opposite, SqlServer to MySql, using the MySql Migration Toolkit (for moving a Fogbugz install from Windows to Linux) and it worked very well. We had trouble with a tool called MSSQL2MySql, it didn't work so well. I'm not sure if the migration toolkit handles the opposite direction, but it might be worth a look.

Eric Z Beard