If I could quote Matt Briggs (it solved my roblem one time):
> The driver way is by FAR the most straight forward. The import/export tools are fantastic, but only if you are using them as a pair. You are in for a wild ride if your table includes dates and you try to export from the db and import into mongo.
>
> You are lucky too, being in c#. We are using ruby, and have a 32million row table we migrated to mongo. Our ending solution was to craft an insane sql statement in postgres that output json (including some pretty kludgy things to get dates going properly) and piped the output of that query on the command line into mongoimport. It took an incredibly frustrating day to write, and is not the sort of thing that can ever really be changed.
>
> So if you can get away with it, use ado.net with the mongo driver. If not, I wish you well :-)
>
> (note that this is coming from a total mongo fanboi)
MySQL is very similar to other SQL databases, so I send You to the topić:
[To see links please register here]