Script file in Schema Compare uses wrong encoding
Script file in Schema Compare uses wrong encoding
I am using the dbforge Schema Compare for Oracle tool but when I generate a script file through Synchronization, the file comes out with an encoding of UCS2-LE BOM which then has to be manually converted to UTF-8 using notepad++. What controls the encoding type when generating a script file through synchronization?
Re: Script file in Schema Compare uses wrong encoding
We will review this and will answer you as soon as possible.
Re: Script file in Schema Compare uses wrong encoding
Are there any updates on this issue?
Re: Script file in Schema Compare uses wrong encoding
Hello,
You can edit the existing connection just set Use Unicode check box in the 'Advanced' tab.
You can edit the existing connection just set Use Unicode check box in the 'Advanced' tab.
Re: Script file in Schema Compare uses wrong encoding
I do have the use unicode check box checked but my sql file is still being set to UCS2-LE BOM.
Re: Script file in Schema Compare uses wrong encoding
Could you please let us know if the 'Use Unicode' check box is selected for both Source and Target connections?
Also, could you please send us the sync script to supportATdevartDOTcom and alexaATdevartDOTcom?
Also, could you please send us the sync script to supportATdevartDOTcom and alexaATdevartDOTcom?