sql server - Porting MS SQL stored procedures to MySQL -


I have around 140 - 150 stored procedures that I need to migrate from MS SQL 2005 to MySQL 5.1

In the last eight hours, I dropped down after successfully assigning 0 of them and asked if anyone has any experience or suggestions, or knows some useful applications that can help.

The MySQL administrator is not very useful, with a disappointing "MySQL error number 1064, you have an error in your SQL syntax; manual that matches your MySQL server version for the correct syntax." Given that an average SP +100 line is long, just thinking what the problem is is not an option.

Example This is an exact error that I get:

  script line: 1 is an error in your SQL syntax; To use near  

, check the manual related to your MySQL server version for the correct syntax, then I have 5 rows:

  Announce the Proof Float; Gartner Group reports that there are manual conversions between two similar lengthy gauges at a rate of around 150. According to the line per day, your rate of progress is only a little lower than the average: -} Worse, it predicts that you have 150 man-days in your endeavor. 

That's why people are automated migration tools that can implement conversion rules in a regular and reliable way. If you are lucky, then someone has done this before you. Those people who want to probably , the pair of conversions is very big, is bigger than those with the set, so usually you are fortunate Are out

The next thing that tells you is "Use regular expression" probably will not work, because you need to create a programmable language, which is not "regular" but "context-free".

One way to get the tool to do this is to use these programmed actions that take a code segment to the second place. They generally require a full language parser, so that instead of action readers, programmers like programmers can work on it.

A good way to write program changes is to use the language's surface syntax as a pattern, essentially "If you see this , then Replace with that . To handle "context-free" issues, consider these as "regular expression".

A device that can accept such surface-syntax program changes, ours.

It takes some effort to record dependable changes. You have some 15,000 lines to convert between the changes in the business, just cutting the pill and working hard, when changing the code For this it is small.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

jquery - SimpleModal Confirm fails to submit form -

php - Multiple Select with Explode: only returns the word "Array" -