Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’d like to give customers a choice of the database engine, but also want to minimize my troubles of such a decision.
The engines in question are MySQL (5 or later) and SQL Server (2005 or later).
Google for the differences in datatypes.
But the schema is just a part of the picture.
The SQL dialects are different too. Google for those differences. Then, either stick to a subset of SQL that’s common to both, or build in a scheme to use somewhat different SQL in each.
Don’t wait until the end to test on the ‘other’ db. Test on both from the start so that you don’t invest too much in a dead end design direction.
Here’s a starting place:
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/mysql.mspx#EZD
and:
http://troels.arvin.dk/db/rdbms/#insert