Implementation Overview - Teradata Database

Tasks 1 through 3 are required on all systems. Other tasks are optional, based on system needs.

1 Make sure you understand how the Teradata Database system handles character data. See “About Character Sets” on page 14 and “About Object Names” on page 17.

2 Determine whether you can use system character set defaults or if you need to configure character set options. See “System Default Character Support” on page 14.

3 Review the object naming topic to understand the rules that determine which characters are valid in object names for your system. See “About Object Names” on page 17.

4 Select and enable the client character sets that you need:

For information about the client character sets for which standard Teradata translation codes are available, see Chapter 2: “Client Character Set Options.”

For information about enabling standard Teradata client character sets, see Chapter 3: “Using Standard Teradata Client Character Sets.”

For information about database (server) character set defaults and options, including setup and usage instructions, see Chapter 4: “Server Character Sets.”

5 If none of the Teradata-standard client character sets meets site needs, you can define a custom (site-defined) client character set:

To create a simple variation of a Teradata standard client character set, see Chapter 5: “Site-Defined Client Character Sets.”

To create an extended client character set with custom character mapping, see Chapter 6: “Extended Site-Defined Client Character Sets.”

6 For information on default collation sequences and how to define and implement custom collation sequences, see Chapter 7: “Collation Sequences.”

7 For detailed information on character conversion between client character sets and the server character set, including the option to define custom export widths for use during conversion to the client character set, see Chapter 8: “Character Conversion.”