Page 1 of 1
Script file in Schema Compare uses wrong encoding
Posted: Thu 19 Jul 2018 16:02
by amochoru
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
Posted: Thu 19 Jul 2018 17:22
by alexa
We will review this and will answer you as soon as possible.
Re: Script file in Schema Compare uses wrong encoding
Posted: Wed 25 Jul 2018 20:12
by amochoru
Are there any updates on this issue?
Re: Script file in Schema Compare uses wrong encoding
Posted: Mon 30 Jul 2018 10:34
by AlexandrS
Hello,
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
Posted: Tue 31 Jul 2018 20:53
by amochoru
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
Posted: Thu 02 Aug 2018 12:04
by alexa
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?