[AccessD] INFO: Why You Should and Should Not Migrate to MySQL

MartyConnelly martyconnelly at shaw.ca
Sun Jul 11 17:35:14 CDT 2004


Just came across this article that gives both points of view

Migrating from Microsoft SQL Server and Access to MySQL

http://dev.mysql.com/tech-resources/articles/migrating-from-microsoft.html

 It also describe briefly some conversion methods and helpful programs

Note that a lot of problems will be resolved by MySQL 5.0 where stored 
procedures, triggers and views have been introduced, although the stored 
procedure
syntax will vary in some degree from Microsoft's T-SQL language. However 
MySQL 5.0 is still in alpha which was released in Febuary. You will have 
problems with the various dialects of SQL like T-SQL from Microsoft or 
PL-SQL from Oracle. It is not plug and play. More like plug and pray.

MySQL Server has many extensions to the SQL standard (so does everyone 
else), but does have a startup switch to use only ANSI SQL:2003 
compliant code.

 MySQL does have a heavier duty database MAXDB from SAP which uses an 
Oracle like SQL syntax, there are perhaps problems with the ODBC bridge to
MAXDB. I have connected to it using Access, but nothing heavy duty. 
Also, there is no OLEDB bridge yet to MySQL, for use with .Net, the 
people I have heard
who know how to write this (they are thin on the ground) want cash to 
write it. Open Source is fine, but not if you have to take off three 
months to write and test this.
Probably MYSQL or SAP will pay for it.

-- 
Marty Connelly
Victoria, B.C.
Canada






More information about the AccessD mailing list