Quote:
Originally posted by kevina
I did some testing and this is indeed an issue.
For now the workaround is to write your sql to a utf-16 file, and submit it from this file instead of from a string (stored inside the step).
Attached is a simple build demonstrating this workaround.
Kevin
|
Thanks - unfortunately my sql code is coming from an input file - so I'd have to write out the contents of that file to a utf-16 file then run the sql command against that. It seems impractical/inefficient/slow for larger files. I'll just write new steps to execute the sql using isql until this is fixed.