Comments
Sort by recent activity
We are having the same problem with sql stored procs, particularly large procs. What we have discovered is that in the Sql Systable, there are missing ASCII 10's after the ASCII 13. This occurs randomly, or seems to. There doesn't appear to be a rhyme or reason. The missing ASCII 10's mess up the line feed and when Sqlcompare creates a script, code lines get placed directly behind comment lines in the destination stored proc. It works fine on the source stored proc.
We are already using Sql compare version 3.
We have talked to Microsoft and they claim that their stored procs are in Unicode and that the ASCII 10's are not needed for a carriage return/line feed. We can recreate the problem by copying the code into Wordpad (works fine in Notepad). They state that since the proc works fine on the source destination, it is not their problem. Since we are copying to a place that is non-Unicode, they cannot help us.
So - is Sqlcompare supposed to be able to deal with this? We use the command-line version to create our script.
If I need to explain further, please tell me what else you need to know. / comments
We are having the same problem with sql stored procs, particularly large procs. What we have discovered is that in the Sql Systable, there are missing ASCII 10's after the ASCII 13. This occurs r...