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

Introduction to the Teradata® RDBMS for UNIX® Version 2 Release 2.1 - NCR

NCR Introduction to the Teradata® RDBMS for UNIX® Version 2 Release 2.1 - NCR, 1998. - 315 p.
Download (direct link): inntroduktionteradata1998.pdf
Previous << 1 .. 49 50 51 52 53 54 < 55 > 56 57 58 59 60 61 .. 76 >> Next

Security and Integrity

For More Information

For More Information

For more information on the topics presented in this chapter, see the following Teradata RDBMS manuals.

IF you want to learn more about . . . THEN see this manual . . .
System administration in general Teradata RDBMS for UNIX Database Design and Administration
Security and security Teradata RDBMS for UNIX Security
administration Administration Guide
Client (TDP) security Teradata TDP Reference

Introduction to the Teradata RDBMS for UNIX

11-15
Security and Integrity

For More Information

11-16

Introduction to the Teradata RDBMS for UNIX
System Administration

Chapter 12

System Administration

Introduction to the Teradata RDBMS for UNIX
System Administration

Introduction to the Teradata RDBMS for UNIX
System Administration

About This Chapter

About This Chapter

Introduction

This chapter covers topics relating to space allocation, accounting, diagnostics and maintenance, and monitoring.

The topics of security and the Data Dictionary are far ranging enough to justify their own chapters. For that reason, those system administration topics are discussed elsewhere in this manual (see Chapter 7, “Data Dictionary,” and Chapter 11, “Security and Integrity”).

Space Allocation

Space allocation for the Teradata RDBMS relates not only to the disk space required for databases, but to the space required to define users as well.

The broad topic of accounting for the Teradata RDBMS includes all Accounting of the following subtopics:

• Users and accounts

• Client accounting

• Server accounting

This topic discusses various aspects of monitoring the Teradata Monitoring RDBMS, including the facilities for performance monitoring.

Introduction to the Teradata RDBMS for UNIX

12-1
System Administration

Space Allocation: Databases and Users

Introduction

Creating Databases and Users

Scenario: Creating Finance and Administration Databases

Space Allocation: Databases and Users

In a Teradata RDBMS, a database is a collection of related tables, views, and macros.

A database also contains an allotment of space from which users can create and maintain their own tables, views, macros, or other users or databases.

A database and a user are almost the same thing in the Teradata RDBMS, the only difference being that a user can log on to the system while a database cannot. A user identifies both someone who can log onto the system and a database.

When the Teradata RDBMS is first installed on a server, there is only one user on the system. Its name is DBC.

This user typically is managed by a database administrator who assigns space from DBC to all other organizations. DBC owns all other databases and users in the system.

To protect the security of system tables within the Teradata RDBMS, the database administrator typically creates a RDBMS administrator user from DBC. The usual procedure is to assign all RDBMS disk space not needed for system tables to the new administrator database.

The database administrator then uses this database as a resource from which to allocate space to the databases and users of the system.

Consider the following scenario: the database administrator needs to create a Finance and Administration (F&A) department database with user Jones as a supervisory user, or database administrator (DBA) within the F&A department.

The Teradata RDBMS database administrator first creates the F&A database, then allocates space from it to Jones to act as the F&A DBA. The Teradata RDBMS DBA also allocates space from F&A to Jones for his personal use and to create a Personnel database and other databases and user space allocations.

Note that when you create a new database or allot space to a user, the system assigns disk space from the space belonging to an existing database or user. The creating database (or user) is the owner of the new database (or user space).

12-2

Introduction to the Teradata RDBMS for UNIX
System Administration

Space Allocation: Databases and Users

The owner permanently grants a specified amount of space to the new database or user, which is then subtracted from the total unused space available to the user.

The following figure illustrates the hierarchy of this relationship.

Figure 12-1 Hierarchy of Users, Databases, and Space Allocation

Introduction to the Teradata RDBMS for UNIX

12-3
System Administration

Space Allocation: Databases and Users

Creating Databases

The F&A Database owns Personnel and all the other department databases. F&A also owns user Jones and all other users within the department. Because the user DBC ultimately owns all other databases and users, it is the final owner of all the databases and user space belonging to the organization.

This hierarchical ownership structure provides the owner of a database or user space with complete control over the security of owned data. The owner can archive the database or can control access to it by granting or revoking privileges on it. For more information on granting and revoking access privileges, see Chapter 11, “Security and Integrity.”
Previous << 1 .. 49 50 51 52 53 54 < 55 > 56 57 58 59 60 61 .. 76 >> Next