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 forUNIX SQL Reference - NCR

NCR Teradata RDBMS forUNIX SQL Reference - NCR, 1997. - 913 p.
Download (direct link): teradataforunix1997.pdf
Previous << 1 .. 132 133 134 135 136 137 < 138 > 139 140 141 142 143 144 .. 241 >> Next

pwd Specifies the password associated with the new user. A password is considered to be a Teradata SQL word and may contain up to 30 characters. Refer to Chapter 4, “Teradata SQL Lexicon”, for a complete description of Teradata SQL ‘words’.
NULL NULL allows the user to logon without a password, as long as the user is authorized by the TDP or CLI.
STARTUP Keyword introducing the clause declaring the startup string.
ing;' tri 'st Specifies one or more SQL statements separated by semicolons, that are executed to establish the session environment when the user logs on. Strings may be up to 255 characters, must be terminated by a semicolon, and must be enclosed by apostrophes. The default is no startup string. A startup string may execute a macro, however, the USING modifier is not supported in a startup string (see Usage Notes). If a string includes a DDL statement, no other statement is allowed in the string. Strings are only executed when you logon through BTEQ or ITEQ.
SPOOL Keyword introducing the bytes allocated to the spool file.

8-96

Teradata RDBMS for UNIX SQL Reference
Teradata SQL Syntax Guide

CREATE USER

Syntax Element... Description
n Specifies the number of bytes (n) to be allocated for spool files. The default is the largest value that is not greater then the owner’s spool space, and that is a multiple of the number of AMPs on the system. n must not exceed the owner’s spool space. n may be entered as an integer, a decimal value, or as a floating point value.
BYTES Optional unit assigned to n bytes allocated to the spool file. n refers to bytes, whether or not BYTES is appended.
DEFAULT DATABASE Keyword introducing the database name, dbname.
dbname Specifies the name of the default database established each time a user logs on the Teradata RDBMS. The username associated with the CREATE USER statement is the default if the DEFAULT DATABASE clause is not specified.
COLLATION Keyword introducing the clause that sets a collation default for the user.
ASCII The default HOST collation is ASCII for configurations other than an IBM channel-attached host. ASCII here refers to Teradata’s extension to the ASCII standard.
EBCDIC The default HOST collation is EBCDIC for an IBM channel-attached host.
MULTINATIONAL MULTINATIONAL is always available in this release. It specifies that the default collation for the user is one of the European (diacritical) or Japanese character (Kanji) sort sequences (see Usage Notes).
HOST HOST specifies that the default collation for the user is determined by the collation of the logon client system. This is the default.
ACCOUNT Keyword introducing the account id identifiers.
'acctid' Specifies an identifier or a list of identifiers of the account(s) that are to be charged for the space used by this user. The first (or only) identifier becomes the default account for the user. If acctid is specified in the logon string, it must have been specified in the ACCOUNT option of the last CREATE USER or MODIFY USER statement for the user. If acctid is not specified, it defaults to the account identifier. Each acctid can be up to 30 characters and must be enclosed in apostrophes. A list of acctids must be separated by commas and enclosed in parentheses.

Teradata RDBMS for UNIX SQL Reference

8-97
Teradata SQL Syntax Guide

CREATE USER

Syntax Element... Description
NO FALLBACK PROTECTION Specifies whether to create and store a duplicate copy of each table created in the new database. The default value is NO FALLBACK. This setting may be overridden for a particular data table when the table is created (refer to “CREATE TABLE” statement). The FALLBACK keyword used alone implies PROTECTION.
NO JOURNAL DUAL JOURNAL BEFORE JOURNAL Specifies the number of before change images to be maintained by default for each data table created in the new database. The JOURNAL keyword without NO or DUAL implies single-copy journaling. If journaling is specified, a DUAL journal is maintained for data tables with FALLBACK protection. The JOURNAL keyword without BEFORE implies both types (BEFORE and AFTER) of images.

8-98

Teradata RDBMS for UNIX SQL Reference
Teradata SQL Syntax Guide

CREATE USER

Maxima

Syntax Element... Description
NO AFTER JOURNAL DUAL AFTER JOURNAL LOCAL AFTER JOURNAL NOT LOCAL AFTER JOURNAL Specifies the type of image to be maintained by default for data tables created in the new database. The JOURNAL keyword without NO or DUAL implies single-copy journaling. If journaling is specified, a DUAL journal is maintained for data tables with FALLBACK protection. NOT LOCAL and LOCAL specify whether single after-image journal rows for non-fallback data tables are written on the same virtual AMP (LOCAL) as the changed data rows, or on another virtual AMP in the cluster (NOT LOCAL). The JOURNAL keyword without AFTER implies both types (BEFORE and AFTER) of images. The default is no journaling If only AFTER JOURNAL is specified, then a before-change image is not maintained. If both types are specified, the two specifications must not conflict. This setting may be overridden for a particular data table when the table is created (refer to “CREATE TABLE” statement).
Previous << 1 .. 132 133 134 135 136 137 < 138 > 139 140 141 142 143 144 .. 241 >> Next