Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 174 175 176 177 178 179 < 180 > 181 182 183 184 185 186 .. 218 >> Next


If the CHARACTER SET attribute is:

KANJI1, then Japanese Character Support is enabled

LATIN, then Standard Character Support is in effect

A - 10

Teradata RDBMS Database Administration Appendix A: Teradata RDBMS Configuration, Global Defaults, and Client Connections

Viewing and Changing International Character Set Settings and Defaults

Client Character Sets

Each client and console platform uses a particular character set during a session to transmit user data. This is the client, or external, character set. No matter which server character set is enabled, communication between the client and Teradata RDBMS is always in the client character set.

Teradata RDBMS translates data strings received from a client into the internal, or server, character set for storage and processing, and translates it back to the client character set when exporting response data to the client. With the exception of the Kanji server character set, this translation allows clients using different character sets to access and modify the same stored data.

Teradata RDBMS offers many pre-defined client character sets (along with the codes for the appropriate collation sequences), and you can define and install your own character set translations and collations. You install client character sets on the server and flag those currently desired as available for use. Also, you can assign an active character set as the default for a client.

You access the dictionary tables to:

Install new character set translation codes and/or collation codes

Activate an installed client character set to make it available for use

Change the default client character set for consoles and/or individual or groups of network-connected clients. (You control the client character sets of channel-connected hosts with an HSHSPB parameter in the TDP.)

Define your own site-defined or extended site-defined client character sets

Note: The ASCII, EBCDIC, and UTF8 character sets are permanently installed and always available.

Viewing the Status of Client Character Sets

Use the system views described below to view the current status of installed international character sets. (For a complete description of these views and their underlying tables, see Teradata RDBMS Data Dictionary.)

View Name Description Reference
DBC.CharTranslations Displays the names of installed character sets. Each name identifies the set of translation tables needed to define the external-internal character mapping for one language. They can be pre-defined, or created by you. Note: Because they are permanently loaded and available, the ASCII, EBCDIC, and UTF8 character sets are not reported. Teradata RDBMS International Character Set Support (includes lists of the mapping and collation codes) For IBM mainframe clients, also see: - "TDP Functionality" on page A-26 - Teradata Director Program Reference

A - 10 Teradata RDBMS Database Administration

Appendix A: Teradata RDBMS Configuration, Global Defaults, and Client Connections

Viewing and Changing International Character Set Settings and Defaults

View Name Description Reference
DBC.HostsInfo Displays the names of the character sets you assigned as the client defaults, by host (LAN connection) or by host group (all LAN connections on a node), in the DBC.Hosts system table. (For mainframe clients, see the HSHSPB parameter block of the TDP.) Teradata RDBMS International Character Set Support (includes lists of the mapping and collation codes) For IBM mainframe clients: - "TDP Functionality" on page A-26 - Teradata Director Program Reference
DBC.CharSets Displays the names of the character sets you flagged in the DBC.CharTranslations table as the ones to activate during a tpareset. These are currently active and available to users at the session level only if a tpareset was performed after you set the flags. Note: A name in this view and CharTranslations does not prove that it is active. The InstallFlag column in CharTranslations is an indication, but can be misleading if the table was changed without a tpareset.

Changing Character Set Defaults

You can control the default client character set and the default server character set at the user level, and the user can choose alternatives during a session.

Default Client Character Set

If you do not define a client character set as the default for a client in the DBC.Hosts table, the automatic default is the character set native to that client.

During a session, the user can find out which client character set is in effect with the SQL HELP SESSION statement, and can specify a different (but active) client character in various ways, depending on the particular client software. With the BTEQ client software, you can use the .SET SESSION CHARSET command. For example:

.SET SESSION CHARSET ASCII

The .SET SESSION command can be entered interactively in the user logon string or at any time during a BTEQ session, or embedded in a BTEQ script file (batch job) or application program.
Previous << 1 .. 174 175 176 177 178 179 < 180 > 181 182 183 184 185 186 .. 218 >> Next