wanted: consultation for migrating from mysql to sql2000 in so california

[mmilano]

Hi Everyone,

I need to port over a php/mysql into php/mssql. php is not the problem, but ms sql 2000 is.

I have several questions on the proper way to implement this and need a few hours of consulting time in the southern california ( south los angeles ) area.

issues include things like how to properly make unique id's such as how mysql can just auto-increment within the database, .. porting the data types, etc...

If are in the area and you feel you are qualified to give proper consultation, please contact me asap.

mmilano@codenewbie.com

Thanks!

[goldbug]

Can't be done remotely?

I'm pretty well versed in both systems (not calling myself an uber-expert, however). Could it be done via this forum (community support), or other means if needed (so-cal is kinda far from the midwest, but I'm bored at work right now and wont mind helping if I can be of use.)

Note:
If you've got Enterprise Manager running, it actually has a somewhat decent import/export data wizard. You can most likely import the data and table structures straight from MySQL (assuming you've got the MySQL ODBC stuff installed). The only thing you will probably end up losing are the auto-incremented field flags (the IDs will be the same, but you will have to go and set the column to IDENTITY(1,1) manually (Identity, seed, increment)), you might lose primary key and indexes, and you might lose foreign key table relationships if you have any set up (only applicable if you used InnoDB or BDB table types instead of the normal/default MyISAM).

As far as data types go, I'd guess the import wizard could guess pretty well (though, I've never gone MySQL > MS SQL). Only types I could imagine being a problem are possibly BLOB/TEXT > IMAGE/TEXT (and their various sizes), and possibly datetime columns (MS SQL usually uses 'MM/DD/YYYY HH:MM:SS AM/PM' format, and MySQL usually takes something along the lines of 'YYYY-MM-DD HH:MM:SS'.


Edit: Added Wizard note.