SQL 2000 to Mysql 5 migration

[yoda]

I've got a client that has a multi user billing system that has a SQL 2000 back end. basically, would like it to go faster and be more stable...

I'm not sure exactly what is sent to the SQL server but it should be just queeries.
I'm just wondering if mysql handles the SQL 'scripting' as well as queeries and if their would be any problems that require changing the way the front end works?

 

[growse]

I'm not sure that MySQL is the answer to "more faster and more stable". What's the cause of the instability, because if it's bad hardware, then moving to a new RMDS isn't really going to help you. Equally with "faster", the answer isn't immediately to jump to a new RMDS. There's a hell of a lot you can do to optimize any database, but what to do will depend on almost everything: schema, amount of data, etc. etc.

Also, not sure what you mean by SQL "scripting" - stored procedures?

Regarding the front end, there are some query syntax differences between the two. If you rely on things like "SELECT TOP 10" on MSSQL, you'll need to change this to a LIMIT statement for mysql.

If it were me, and I was going from MSSQL to something, I'd pick postgres or oracle. People don't tend to use MSSQL unless they're going to use the nifty enterprisy features of it, most of which MySQL can't do (as far as I'm aware....).