- BMP from Unicode versions 6.1.0 to 9.0.0, which Teradata does not support, including emoji
- SMP from all Unicode versions, which Teradata does not support
- Unassigned characters
- Private use characters
UTF-8 or UTF-16 sessions with Unicode Pass Through enabled allow pass through characters to be used in requests and to be stored in or retrieved from Unicode columns. Noncharacters and characters with an invalid encoding form are changed to the REPLACEMENT CHARACTER (U+FFFD), which can pass through and be stored in Teradata with this option.
BTEQ Example with Unicode Pass Through
.SESSIONS 5 .LOGON mysystem/uptuser,emoji .REPEAT 5 SET SESSION CHARACTER SET UNICODE PASS THROUGH ON;
Teradata Parallel Transporter Example with Unicode Pass Through
VARCHAR UnicodePassThrough = ‘ON’,
- SQL Inserter
- SQL Selector
JDBC Example with User Startup String
create user uptuser as password = emoji, startup = ’set session character set unicode pass through on’; Connection con = DriverManager.getConnection("jdbc:teradata://dbs/RUNSTARTUP=ON", "uptuser", "emoji");
JDBC Example with SQL Request
stmt.executeUpdate("set session character set unicode pass through on");
Teradata Studio Example
In the Studio Administration Create User form, provide a startup string, such as “set session character set unicode pass through on".
When creating the connection profile for that user, add the JDBC property RUNSTARTUP=ON.
- Customers should not use Unicode Pass Through if they rely on Teradata to screen out Teradata unsupported characters.
- You may have existing processes in place to cleanse Unicode data before loading it into Teradata Database, such as access modules and UDFs. To take full advantage of Unicode Pass Through, you must change or eliminate prior methods of cleansing Unicode data before loading. See the TPT documentation for details on configuring how TPT uses access modules. For details about configuring access modules to allow pass through characters, see Teradata Tools and Utilities Access Module Reference, in particular the sections regarding automatic character conversions.
For More Information
For the syntax of using SET SESSION CHARACTER SET UNICODE, see SQL Data Definition Language - Syntax and Examples. For further details on Unicode Pass Through, see International Character Set Support.