BUG: Extended ASCII characters in strings cause errant behavior

Brian Donahue

Hi Brian,

Thanks for your post. There's actually a small problem with saving
scripts in SQL Compare, SQL Data Compare, and SQL Packager. The UTF-8
preamble to the text file is not written by the software, resulting in some
confusion by programs like Query Analyzer when they open and read the file.
Query Analyzer does not expect Unicode characters in the script because of
the missing preamble, but they exist in the script nonetheless.

This problem will be fixed in the upcoming version. In the meantime, the
workaround is to load the script into Notepad, then save it again as a UTF-8
text file. This will rebuild the missing preamble so Unicode-aware programs
like Query Analyzer will know to expect Unicode data in the file.

Regards,

Brian Donahue
Red Gate Technical Support


"Brian Adams" <brian.adams@ninaza.com> wrote in message
news:%23KneGo7gEHA.2632@server53...
> We have several stored procedures with embedded string literals like
> 'somename®'. When using SQLPackagers 'Save Script' feature, the resulting
> output mangles the embedded string usually adding other characters like
> 'somename®'.
>
> Saving the package as a .exe and running it works correctly.
>
> SQL Compare correctly shows that the stored procedures are identical. SQL
> Package manager still reports the stored procedures are not matching.
>
> I have not been able to find an option that will change the SQL Package
> manager behavior.
>
> Regards,
>
> Brian Adams
> Ninaza
>
>