Changed to SQL Server - types problems

Hi Folks - we just had a ‘Client’ enforced change from MySQL to SQL Server - and since we were unable to get an export of the solution to import to a workspace with SQL Server as the Db we used a migration tool to get the data across.

Immediately we’ve had significant challenges with SQL code in datasets and had to redevelop most of them to suite MS SQL nuances. Hadn’t realised MySQL was so loose on SQL style!!!

Next big problem is with data types. Looks like .getTime() does not work with the date types we have now and media types text, ntext and others are throwing errors - all of which worked fine before the data port.

Has anyone experience with the different types in a cross over like this? Or perhaps any advice to get an import of a solution to run in a SQLServer environment (we did successfully do this with SQLServer 2005 last year but this is 2008 and it seems quite a bit different).

UPDATE: Now done a full import of the solution and we get the same data type issues everywhere? BTW We dint drop the tables just imported new.

Kahuna:
Immediately we’ve had significant challenges with SQL code in datasets and had to redevelop most of them to suite MS SQL nuances. Hadn’t realised MySQL was so loose on SQL style!!!

To use an understatement, MySQL (especially out-of-the-box) is not very standards compliant.

Kahuna:
Next big problem is with data types. Looks like .getTime() does not work with the date types we have now and media types text, ntext and others are throwing errors - all of which worked fine before the data port.

Before you also used .getTime() of date fields ? Date columns don’t have a time component, they are dates only. I think you want to use a datetime datatype or a timestamp datatype instead.

Kahuna:
UPDATE: Now done a full import of the solution and we get the same data type issues everywhere? BTW We dint drop the tables just imported new.

Importing a solution won’t drop- or change column datatypes, it will only add new tables/columns.