It’s worth making a note of characterset issues as we come across them.
Let’s say I have some data in SQL Server:
SELECT 'Jörg' AS Name UNION SELECT 'Jones' AS Name
Great, now we have this unicode file and we need to import it, for the unicode character to be supported by Oracle SQL Developer there is a setting you may need to change.
With the default setting of Cp1252:
when I open the test.csv I see:
Those with a keen eye will spot the Byte Order Mark (BOM), but ouch, look at what has happened to Jörg.
The Oracle SQL Developer Data Import Wizard can trick you too, if Encoding setting is set to default then it won’t be the UTF-8 we’ve set, you will need to manually change this to UTF-8 each time you do an import: