I’m not the only one with this problem. Greg Knierim posted some feedback to the VS 2008 team about what appears to be the exact same issue.
At this point I think I have two options:
- Assiduously save each .sql file in code page 1200 (Unicode, UTF-16)
- Write up some garbage script in my custom MSBuild task that saves the input files in an acceptable encoding before SQLCMD gets to them.
Any other ideas?