Manual migration from MS SQL Server to MySQL
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."
If you got lots of stored procedures (Transact SQL or whatever MS SQL uses these days) then you're in for a world of hurt.
Not to mention that MySQL doesn't even enforce referential integrity would would seem much less functional than MS SQL.
I would maybe move to Postgress if you are looking for something on the cheap. I don't understand why MySQL has such a following, it's not that great as for as databases go. Barely a step above Berkley DB.
Is it practical to switch from SQL Server to MySQL? MySQL doesn't even have views! I can't imagine any scenario where one would want to take the big hit in features, except if you absolutely needed more speed, and didn't have a need for the features. Still, it would make more sense to switch to PostgreSQL since it has as many, if not more, features than SQL Server.
This is the kind of news that PHBs need to hear. These types of migrations are possible! I plan to write some similar articles on migrating some other proprietary produces to F/OSS software, including:
Microsoft Office --> VI
ASP.NET --> sh scripts
Peachtree Accounting --> GnuCash
PeopleSoft --> awk
Rational Rose --> GIMP