0

Resolved

Sql encoding

description

Hi Chao,
 
The encoding issue is fixed in VulcanRelease version. Could you merge the changes from ‘VulcanRelease’ to ‘Vulcan’?
Another question, we use ‘UTF-32’ encoding in the new codes. It could fix the issue(See the attached e-mail).
But the saved .sql file is not well compatible with SSMS(The SQL queries can’t be executed in SSMS). It makes more difficult to debug the SQL queries.
Do you think if there’s a better encoding format which could both fix the issue and  be compatible with SSMS?
 
Thank you!
 
Aaron Zhang
CSS BI China

comments