MySQL to MS SQL

MySQL to MS SQL

Postby ekarasu » Wed 01 Feb 2006 06:05

Our product is working with MySQL (using MyDAC component) and we want to develop another version for MS SQL. My question is, is it easy to convert the current project for MSSQL using SDAC component? What are the important and painful issues in conversion? Ercan
ekarasu
 
Posts: 15
Joined: Wed 01 Feb 2006 05:56

Postby Bernhard Geyer » Thu 02 Feb 2006 07:00

Modify your application to use the Bridge-Pattern to encapsulate the DB-Access-Layer. All DB-Specifiy Code should be in only one unit.

If you have don this, you can add MS SQL-Support by adding one unit with using SDAC.
Bernhard Geyer
 
Posts: 20
Joined: Fri 30 Sep 2005 14:13

Postby ekarasu » Thu 02 Feb 2006 08:00

Does SDAC cover all the functions MyDAC has? I mean even if we do it with a DB layer, will there be additional precautions that we have to take for implementing certain functions (like backup, repair or table data type adaption)?
ekarasu
 
Posts: 15
Joined: Wed 01 Feb 2006 05:56

Postby Ikar » Mon 06 Feb 2006 10:27

SDAC is similar to MyDAC but there are some differences that depend on the SQL Server functionality and on the users' demand. For example: you can't use DROP ... IF EXISTS statement, because MSSQL Server doesn't allow this functionality.
Ikar
 
Posts: 1693
Joined: Thu 28 Oct 2004 13:56

Postby Ikar » Mon 06 Feb 2006 12:07

Some actions, like backup, repair etc are implemented on different servers in different ways. Therefore you should implement managing of these actions separately for each server (MySQL Server, MSSQL Server etc).
Ikar
 
Posts: 1693
Joined: Thu 28 Oct 2004 13:56


Return to MySQL Data Access Components