I'm building a SP that uses the BCP command to create a file with the -w option.
I then am able to load the file into a table using the same options.
What I'm trying to understand is the following:
When I open the file in TextPad, I see the file type as Unicode
When I open the file in editpad pro, I see the file type as UTF-16
reading on the web, If I understand correctly, BCP -w spits out files that are UTF-16LE... Is this correct?
based on , the difference between UTF-16 and UTF-16LE is:
"UTF-16 and UTF-32 use code units that are two and four bytes long respectively. For these UTFs, there are three sub-flavors: BE, LE and unmarked. The BE form uses big-endian byte serialization (most significant byte first), the LE form uses little-endian byte serialization (least significant byte first) and the unmarked form uses big-endian byte serialization by default, but may include a byte order mark at the beginning to indicate the actual byte serialization used.
How does this affect our SQL Servers?
This can only affect developers if they read the files, right? or does affect the tables that are loaded by the bcp?