Slashdot Mirror

← Back to Stories (view on slashdot.org)

Manual migration from MS SQL Server to MySQL

Posted by timothy on from the minimizing-handwork dept.

Mark Brunelli, News Editor writes "It's no small feat to manually migrate an enterprise from Microsoft SQL Server to MySQL, but it can be done. Here, Mike Sheffey, CEO of Versora, gives step-by-step instructions for two manual tasks: moving the data structure and the data itself."

4 of 44 comments (clear)

  1. Re:Practical? by the+eric+conspiracy · · Score: 2, Informative

    Is it practical to switch from SQL Server to MySQL?

    I guess it depends on how minimal your needs are. But one thing I have noticed is that MySQL maps better to MS-SQL than Postgres. Postgres maps better to Oracle.

  2. Re:Practical? by youknowmewell · · Score: 2, Informative

    True, and MySQL can be alot cheaper as well. Still, the flexability PostgreSQL gives for future feature needs (without the need to migrate AGAIN) seems to appeal to me more than MySQL's features (or lack thereof).

  3. Re:Practical? by the+eric+conspiracy · · Score: 2, Informative

    How so? Is it because of dialectic or feature reasons?

    For example PG and Oracle use sequences, MySQL and MS use autoincrement fields.

  4. Re:Uh, for simple databases maybe by jpkunst · · Score: 3, Informative

    Not to mention that MySQL doesn't even enforce referential integrity would would seem much less functional than MS SQL.

    Will people ever stop saying this? InnoDB tables, which provide referential integrity, have been available for MySQL since version 3.23.34a (2001), are included in binary distributions by default as of MySQL 4.0, and are the default table type on Windows starting with version 4.1.5. See InnoDB Overview.

    JP