| Team Fly | |
Most of us are familiar with accounts' usernames and passwords from our experience logging into corporate networks and other secure systems. Oracle Database 10g implements the same mechanism with login credentials and privileges given out by the database administrator. Once accounts are created, people initiate connections to the Oracle Database 10g and work with their own data and other users' data where the appropriate privileges have been given out. We discuss object privileges in the ''Work with Object and System Privileges" section immediately following this one.
NOTE
With Oracle Database 10g, the terminology user, account, and schema are used synonymously.
Once an account is created, it is often given the rights to occupy space in one or more Oracle Database 10g tablespaces. This is discussed next.
As additional non-system tablespaces are created, the database administrator gives out quotas that allow users to occupy space therein. Tablespace quotas are given out using an SQL statement with three parts:
The username to whom the quota is being given.
The name of the tablespace within which the username is being permitted to create tables.
The amount of that quota—be it mentioned in absolute bytes (for example, 500,000) or more commonly in quantities of megabytes (500MB, for instance). Unlimited quotas can be allowed using the keyword unlimited.
Regardless of how a quota is given out, the SQL statement passed to Oracle Database 10g resembles the following:
SQL*Plus: Release 10.1.0.1.0 - Production on Sun Mar 11 10:29:42 2007 Copyright (c) 1982, 2003, Oracle. All rights reserved. Connected to: Oracle10g Enterprise Edition Release 10.1.0.1.0 - Production With the Partitioning, OLAP and Data Mining options SQL> alter user hr quota 500m on hr_data; User altered. SQL> alter user ap quota unlimited on ap_idx; User altered.
| Team Fly | |