Doug Brown wrote:
> I am wondering how difficult it might be to migrate over to mySql from 
> SQL2000? Is this a daunting task? Any assistance would be much appreciated. I 
> would especially love to hear from someone who has done this.
>
>   
I did this a year ago with a very large application.  We didn't have a 
whole lot of tricky stuff to convert - no stored procedures, full text 
indexes, etc.  These are possible with MySQL, but the syntax probably 
differs.

I mostly remember changing all my "Top N"s to "LIMIT N", and getting rid 
of a lot of cast()s and convert()s that we had to use with SQL Server 
(no longer necessary, the comparisons just worked in MySQL).  Also had a 
lot of places where I was selecting @@IDENTITY after creating a record, 
mysql uses a different syntax to get the last inserted record ID.  Also 
we had been sometimes placing more than one SQL statement in a cfquery 
block (delete all, loop and insert, etc.).  This can be done with MySQL 
but at the time I don't think the driver supported it.  So those had to 
be broken out into separate cfquery blocks.

I used the Intelligent Converters kit, it was well worth the $49 bucks. 
http://www.convert-in.com/mss2sql.htm

In the end it was definitely worth it, we were paying some hefty yearly 
fees for both the OS and the SQL Server license.  I believe this is the 
direction MS is moving, where you have to pay every year.  We would have 
started off with MySQL in the first place but at the time it didn't 
support transactions.

-Ryan


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:258458
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to