Re: Sybase isql converter

Such a converter exist to convert Sybase Transac-SQL to Informix SPL. Ask your local informix representative that will provide you the tools required. I have worked on these tools and successfully converted up to 30+ACU- of our Sybase SQL procedures without need to rewrite them, at least for the first release. Then it required many enhancements to the converter, and I have completely revamped it to satisfy our needs for up to 95+ACU- of our procedures (on 600 and more Sybase procedures, only 12 had to be patched manually, mainly due to semantics difference of some Sybase constructs like ambiguous +- operator for string concatenation or numeric addition, concatenation of NULL-possible values). Then I have written the support procedures that allow unlimited use of Sybase constructs in Informix SQL language: explicit conversions, handling substring(), isnull(), datetime conversion styles. Because I did it with the aggreement of Informix I am not authorized to communicate it directly, but may be my work has been trnasmitted by my local Informix representative to the Informix world as a successfull conversion. However expect at least a step in optimizing and controlling the results of the conversion. The Informix converter now is much better than ever, cleaner, uses non ambiguous and complete LALR grammar for Sybase Transac SQL with no shift/reduce and no reduce/reduce ambiguity, smarter when it generates the effective SQL code: automatic handling of SET ROWCOUNT constructs, detection of multiple result sets, support for compound-join updates and deletes, near complete support for most of Sybase cursors declared in the procedure, ... Beware during the conversion to Sybase recursive procedures that use temporary tables (Informix temporary tables are local to the session, not to the procedure call instance like Sybase). Such procedures, often used to handle data organised as trees, will have to be rewritten using non-recursive algorithms using loops and may be an auxiliary work table to simulate the recursion call stack. I have experimented that rewriting those Sybase procedures without recursion also gained (much) in performance in Sybase while gaining also in portability to Informix and Oracle. Beware of Sybase ISQL scripts that manage the data dictionary. Most of such scripts use non portable SQL like calling system stored procedures specific to Sybase, creating storage devices, and so on... Use a case tool like AMC Designor to manage this conversion. Mike McCaslin a +AOk-crit dans le message ... +AD4-I have some Sybase SQL that I need to convert to run with DBaccess. Does +AD4-anyone know of a conversion program?