What should I expect when migrating custom applications from SQL Server to MySQL?

What should I expect when migrating custom applications from SQL Server to MySQL?

What compatibility problems should I expect to run into when moving my customer's custom applications from SQL Server to MySQL? Do you have any tips for compatibility testing?

To continue reading for free, register below or login

Requires Membership to View

To gain access to this and all member only content, please provide the following information:

By submitting your registration information to SearchSystemsChannel.com you agree to receive email communications from the TechTarget network of sites, and/or third party content providers that have relationships with TechTarget, based on your topic interests and activity, including updates on new content, event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile, unsubscribing via email or by contacting us here

  • Your use of SearchSystemsChannel.com is governed by our Terms of Use
  • We designed our Privacy Policy to provide you with important disclosures about how we collect and use your registration and other information. We encourage you to read the Privacy Policy, and to use it to help make informed decisions.
  • If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States.

Microsoft SQL Server, while a powerful feature rich relational database management system (RDBMS), does have very high licensing costs -- especially if you are using the Enterprise Edition per-processor licensing mode. Using an open source RDBMS like MySQL makes sense when you are doing simple transactions and do not need advanced troubleshooting tools or reporting, notification, OLAP or other components. If you are considering MySQL for your clients' enterprise, be sure you read the MySQL gotchas before deploying MySQL.

MySQL may have a place in the enterprise -- for example, Yahoo uses Oracle as its primary RDBMS but has a large implementation of MySQL for some of its back-end processes.

If you're migrating from SQL Server to MySQL, ensure that MySQL does provide you with the same or acceptable performance and that the solutions you propose will provide the same level of functionality that was delivered by SQL Server. MySQL has different data types. When exporting your data to MySQL from SQL Server, ensure that the data is converted correctly. DTS and SSIS, or your favorite ETL package, can be helpful.

MySQL does not support the same feature set as SQL Server: Security is rudimentary, and MySQL only started supporting stored procedures, subqueries and views in Version 5; however, the stored procedure will likely need to be rewritten in MySQL. Functions are different in MySQL than in SQL Server. Some of the built-in system functions have different names in MySQL than in SQL Server.

This was first published in July 2007