CHARACTER and GRAPHIC Server Character Set Limitations for INSERT Operations

CHARACTER and GRAPHIC Server Character Set Limitations for INSERT Operations - Teradata VantageCloud Lake

Lake - Working with SQL

Deployment

VantageCloud

Edition

Lake

Product

Teradata VantageCloud Lake

Release Number

Published

February 2025

ft:locale

en-US

ft:lastEdition

2025-11-21

dita:mapPath

jbe1714339405530.ditamap

dita:ditavalPath

pny1626732985837.ditaval

dita:id

jbe1714339405530

This table describes the data limits on INSERT operations for CHARACTER and GRAPHIC server character sets.

Client Character Set Type	USING Data Type	Maximum Size for USING Data	Server Character Set	Maximum Column Size for INSERT (Characters)
Single byte	CHARACTER	64,000 bytes	LATIN	64,000
			KANJI1	64,000
			UNICODE If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the characters that exceed that limit are truncated. This includes Unicode data in both UTF-8 and UTF-16 sessions.	32,000
			KANJISJIS If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the characters that exceed that limit are truncated.	32,000
Multibyte	CHARACTER	64,000 bytes	LATIN If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the system rejects the row. Although a Latin field can be defined as 64K, you cannot insert more than 32K multibyte characters into the field because the database uses Unicode internally, and Unicode has a 32K limit. The load utilities are similarly limited.	32,000
			KANJI1	64,000
			UNICODE If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the characters that exceed that limit are truncated. This includes Unicode data in both UTF-8 and UTF-16 sessions.	32,000
Multibyte	CHARACTER	64,000 bytes	KANJISJIS If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the characters that exceed that limit are truncated.	32,000
	GRAPHIC	32,000 characters	GRAPHIC	32,000
			LATIN If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the system rejects the row. Although a Latin field can be defined as 64K, you cannot insert more than 32K multibyte characters into the field because the database uses Unicode internally, and Unicode has a 32K limit. The load utilities are similarly limited.
			KANJI1
			UNICODE If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the characters that exceed that limit are truncated. This includes Unicode data in both UTF-8 and UTF-16 sessions.
			KANJISJIS If the USING data row contains more than 32K logical characters (or more than 64K bytes when mixed single-byte-multibyte strings are involved), the characters that exceed that limit are truncated.