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 .. 18 19 20 21 22 23 < 24 > 25 26 27 28 29 30 .. 218 >> Next

Space type:
Permanent Not Not mandatory, but required if the user wants
mandatory, to create objects. However, space is not needed
but required for a user to access other databases and create
if objects are views and macros on tables in other databases,
to be created depending on the privileges the owners of the
in this space other databases granted to that user.
Spool Not Not mandatory, but required to hold query
mandatory, responses and to execute most things. It is also
but required needed to use volatile temporary tables.
if users are
allocated
from this
database
Temporary Not Not mandatory, but required if user needs to
mandatory, materialize global temporary tables.
but required
if users are
allocated
from this
database
Stored Not mandatory. Stored procedures must be associated with a
procedures Database/User but a Database/User is not required to have stored
procedures.
The system cannot create a stored procedure in a Database/User until
permanent space is assigned to that Database/User.
Tables Not mandatory. Tables must be associated with a Database/User but a Database/User is not required to have tables. The system cannot insert tables into a Database/User until permanent space is assigned to that Database/User, except for volatile temporary tables. (Global temporary tables require permanent space for the table header row.)

1 - 10 Teradata RDBMS Database Administration

Chapter 1: Database Hierarchy

Databases versus Users

Object or Parameter Database User
Triggers Not mandatory. Triggers must be associated with a Database/User but a Database/User is not required to have triggers. Permanent space is not required.
Views Not mandatory. Views must be associated with a Database/User but a Database/User is not required to have views. Permanent space is not required.

1 - 10

Teradata RDBMS Database Administration Chapter 1: Database Hierarchy

Owners, Parents, and Children

Owners, Parents, and Children

As you define users and databases, a hierarchical relationship among them will evolve.

When you create new objects, you subtract permanent space from the assigned limit of an existing database or user. A database or user that has space subtracted from its own permanent space to create a new object becomes the immediate owner of that new object.

An "owner" or "parent" is any object above you in the hierarchy (note that you can use the terms owner and parent interchangeably). A "child" is any object below you in the hierarchy. An owner or parent can have many children.

The term "immediate parent" is sometimes used to describe a database or user just above you in the hierarchy.

For an example of how this hierarchy works, see "Creating a Database or User" on page 2-2.

Teradata RDBMS Database Administration

1 - 13 Chapter 1: Database Hierarchy

Databases versus Users

Creator versus Owner

The creator of an object is the user who submitted the CREATE statement. Every objectobject has one and only one creator.

Note: If the CREATE statement is executed within a macro, then the user who executed the macro is the creator of the object. The macro is just a vehicle for that creation.

The owner of an object is the database in which that object was created. The default is the database of the creating user, but the user can specify a different database by fully qualifying the object (preceding the object name with the database name and a period seperator, as databasename.objectname) in the CREATE statement.

The owner of a new user is the database space from which the new user's PERM space was allocated. The default is the creator (the user submitting the CREATE statement), but that user can specify a different database with the FROM DATABASE option of the CREATE USER statement. (For details, see "Creating a Database or User" on page 2-2.)

The basic rules defining a creator, an owner, and an immediate owner are as follows:

IF . THEN .
you execute a CREATE statement that creates an object (anywhere in the Teradata database) you are the creator of that object. You are not necessarily an owner, or the immediate owner, of that object.
an object is directly below you in the hierarchy you are the immediate owner of that object
you create an object in your own default database you are both the creator and the immediate owner of that object
you create an object in another user's space (assuming you have the privilege that allows you to do so) You are the creator of the object The other user is the immediate owner of the object
A user is the owner of another (subordinate) user The subordinate user creates an object in his or her default database The subordinate user is the creator ot the object The subordinate user is the immediate owner of the object The owner of the subordinate user is also an owner, but not the immediate owner, of the object

When using roles, privileges also can be inherited. For details, see "Access Privileges" on page 6-2.
Previous << 1 .. 18 19 20 21 22 23 < 24 > 25 26 27 28 29 30 .. 218 >> Next