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 .. 175 176 177 178 179 180 < 181 > 182 183 184 185 186 187 .. 218 >> Next


Default Server Character Set

You can specify the default server character set for a user via the optional DEFAULT CHARACTER SET clause of the CREATE/MODIFY USER statement. If this clause is not specified, the DEFAULT CHARACTER SET for the user is determined by the language support mode.

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

For example, if the language support mode is Standard, the default server character sets for data submitted by that user is LATIN.

Note: For columns described as data type CHARACTER, the user can override the server default at the table level with the CHARACTER SET attribute of the CREATE TABLE statement.

Changing Collation Defaults

You can define the default collation sequence for a user with the COLLATION clause of the CREATE/MODIFY USER statement. Teradata RDBMS provides a number of small but flexible sets of collations to choose from. For example, CHARSET_COLL produces a binary ordering based on the current character set; MULTINATIONAL collation can be tailored as needed.

If you do not define a default collation for the user, the automatic default is EBCDIC for IBM mainframe (channel-connected) clients and ASCII for all others.

During a session, the user can override the user or current session default with the SQL statement SET SESSION COLLATION. For example:

SET SESSION COLLATION JIS_COLL;

For a full explanation of Teradata RDBMS collating conventions and instructions on how to define your own sequences, see

"ORDER BY Clause" in Teradata RDBMS Reference, Volume 6

"Comparison Operators" in Teradata RDBMS SQL Reference, Volume 5

Teradata RDBMS International Character Set Support

A - 10 Teradata RDBMS Database Administration

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

Cultural Format Defaults

Cultural Format Defaults

Tunable defaults for the output format of cultural (locale-specific) data types are globally defined in a Specification for Data Formatting (SDF) text file named tdlocaledef.txt.

The file provides a method of defining the output format of data types such as DECIMAL, BYTEINT, SMALLINT, INTEGER, REAL, DATE, TIME, and TIMESTAMP. The definition file also allows you to specify numeric group and fraction separator characters, primary and dual currency symbols, and grouping rules and variable-width groups for numbers and text strings.

Note: The global defaults are pre-defined in the SDF file based on your specifications when you ordered your Teradata RDBMS. The contents of the file are loaded during installation and typically are not changed in a production environment. However, you can redefine them as necessary using the tdlocaledef utility (see "Viewing or Modifying the Teradata RDBMS Configuration" on page A-13 and Teradata RDBMS Utilities).

The global definitions set by the SDF file can be overridden on a per-user basis with the SQL FORMAT phrase. The FORMAT phrase accepts a wide range of directive characters for handling output formats, including:

Order of month, day, and year

Abbreviated and full names of days and months in native language

Twelve-hour time plus order of hour, minute, second, and time zone

Variable-width groups and separator characters for groups and fractional portions of numbers

Euro currency format, primary and dual currency names in native format, and currency symbols in native and ISO format

For FORMAT syntax and usage details, see "Output Format Phrases" in Teradata RDBMS SQL Reference, Volume 3.

A - 12

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

Viewing or Modifying the Teradata RDBMS Configuration

Viewing or Modifying the Teradata RDBMS Configuration

A Teradata RDBMS configuration includes the following components:

Hosts (clients), which can be any combination of multiple:

Channel-connected (mainframe) clients

Gateway-connected (network) clients

Parsing Engine (PE) vprocs

Access Module Process (AMP) vprocs

Each node contains:

This map . Describes the .
current configuration current arrangement and status of vprocs in the Teradata RDBMS Trusted Parallel Application (TPA).
new configuration changes and additions to and deletions from the current configuration.

This section explains the configuration maps and how to display or change the configuration, and provides some reconfiguration guidelines.

Caution: The placement of AMPs and PEs in a configuration is critical to the overall performance of Teradata RDBMS. Consult the TSC to resolve questions or issues before starting the Configuration, Reconfiguration, or pdeconfig utility.

Configuration Maps

The configuration maps are the working areas in a node. A configuration map:
Previous << 1 .. 175 176 177 178 179 180 < 181 > 182 183 184 185 186 187 .. 218 >> Next