ANSI vs Unicode

Brian Donahue

Hi Scott,

Thanks for your post. The scripts that SQL Compare 3 produces are meant
to be ANSI, but for some reason a UTF preamble got appended to the beginning
of the text stream. That's been fixed for the next release, but for now,
you'll have to lop off the first two bytes of the script somehow. If you're
using isql.exe to run the script, consider using osql.exe, which supports
Unicode.

Query Analyzer has a limitation of 1MB of data that we can send into the
program, which is why you get the error message when you try to send a large
script to it. That would also explain the default option of running the
script from inside SQL Compare.

Please let us know if you have any more questions or suggestions.

Regards,

Brian Donahue
Red Gate Technical Support

"Scott Tucholka" <scott.tucholka@aqssys.com> wrote in message
news:VItdOMtBEHA.1468@server53...
> Just purchased 3.10 of SQLCompare.
>
>
>
> We previously were using 2.03, and the scripts were created in ANSI, but
the
> new version produces Unicode. Do not see an option to set the scripts to
be
> created in ANSI, or Unicode. We port the created scripts to an installer
> that cannot handle the Unicode. Any suggestions?
>
>
>
> Also, I noticed that the default in the Synchronize Action is to
> 'Synchronize databases now'. Has anyone else suggested that 'Launch SQL
QA'
> would be the better default? It would be very easy to do something bad. Is
> there someway to change this setting? Why is the message 'Script size more
> than 1M' and Launch QA grayed out? Almost all of our scripts are over that
> size.
>
>
>
> Otherwise the compares went from over two hours to around three minutes,
> very cool.
>
>
>
> Scott
>
>
>

Brian Donahue

SQL Compare 3.15 had introduced a dropdown list in the save script dialogue. Now it is possible to save scripts as ASCII, UTF-8 (with or without preamble) or Unicode. This would definitely solve Scott's problem.