Comments
1 comment
-
I believe that SQL Source Control saves the files as UTF8 without Byte Order Marker. I can put in a suggestion that the files are saved with BOM but I don't know if there is a good reason why they don't do that already.
Is the error you mention in the beginninng definitely caused by an incorrect conversion of the text into the correct locale?
Add comment
Please sign in to leave a comment.
Source Compare window will got garbled, then show error message
Error file : C:\Users\Administrator\.......\XXX.sql
When I try to open the file using SSMS , SSMS will got the garbled too. And I found the file not have BOM.
I try to append BOM by manual, the file will open normal .
My language is zh-TW, and using SQL 2008 R2 SP1
Thanks for your helping...